ArC: add validation of synthetic bean types

[Ladicek]

So far, bean types of synthetic beans were not validated, so it was possible to create synthetic beans with illegal bean types. This commit fixes that. If a synthetic bean has an illegal type, definition error occurs.

Fixes #46771

[Ladicek]

One question I have is: in case of declared beans, illegal bean types don't cause a definition error, they are just removed from the set of bean types. It seems to me that in case of synthetic beans, it is better to fail immediately, because the types are not discovered by the container, they are added by the user, so they probably want to know they're doing something wrong. But it is not consistent with other kinds of beans.

[mkouba]

One question I have is: in case of declared beans, illegal bean types don't cause a definition error, they are just removed from the set of bean types. It seems to me that in case of synthetic beans, it is better to fail immediately, because the types are not discovered by the container, they are added by the user, so they probably want to know they're doing something wrong.

I do agree.

But it is not consistent with other kinds of beans.

It's not the only inconsistency between synthetic and regular beans 🤷.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 37e8e28.

✅ 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.

[manovotn]

It seems to me that in case of synthetic beans, it is better to fail immediately, because the types are not discovered by the container, they are added by the user, so they probably want to know they're doing something wrong.

Definitely agree, thanks for the PR and tests 👍