Create a test that covers the situation described in detail in #342:
- a custom
HttpAuthenticationMechanismHandler annotated with @Alternative @Priority to enable it
- 2 OIDC mechanism definitions - multiple combinations: one with the default qualifier, the other one with a custom qualifier; both with custom qualifiers; both defined on a single class; defined in 2 separate classes
- Inject both OIDC mechanisms into the custom handler via qualifiers
Optionally also create similar tests for other mechanisms, like Basic and Form. Or a test that combines many mechanisms, e.g. 2 Basic, 3 Form, 2 OIDC.