Qute: support synthetic named CDI beans injected in templates

[mkouba]

• this requires an additional late initialization of the QuteContext bean

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 31848b8.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[ia3andy]

Thanks for this @mkouba, I am testing it now.

It would be nice if we could have a new kind of Supplier for synthetic beans, let's call them InitSupplier (InitializableSupplier) which takes two types as generic type <InitType, SuppliedType> which extends Supplier<SuppliedType> but with an extra setter for InitType. This would allow:

1. To hide the setter from the user api
2. To have a common buildtime check buildstep to make sure the data is initialized by the extension

I also had a case with a similar Cycle issue due to synthetic beans and had to provide a similar workaround.

[ia3andy]

I've tested it and it works well! @mkouba do you think it's safe to backport it to 3.13.0?