Create a TCK test for multiple OIDC mechanisms

Create a test that covers the situation described in detail in https://github.com/jakartaee/security/issues/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.

Read the detailed scenario in issue 342 first, then inspect the Jakarta Security TCK's existing authentication-mechanism tests and entry points. Cover the listed OIDC combinations, including qualifier injection into a prioritized alternative handler, and verify the tests pass. Treat the optional Basic and Form cases as follow-up scope.

Written by the indexing model from the issue text.