quarkus-oidc should start without Keycloak and having to disable the tenant

[sberyozkin]

Description
Right now quarkus-oidc can start without Keycloak (other OIDC provider) if quarkus.oidc.tenant-enabled=false for the default configuration/tenant. This poses a problem for the dev mode in particular. It is not consistent with the fact that the dynamic tenants can be easily allocated at runtime with TenantConfigResolver with Keycloak not even being available at the start up.
quarkus.oidc.tenant-enabled can remain to be useful on its own - but quarkus-oidc should be able to start even if the default tenant is enabled and Keycloak is not available - it has been proposed by some users before.

Implementation ideas
OidcRecorder should avoid resolving Uni for the default and other statically configured tenants and delay it till the tenant is requested at runtime

[quarkus-bot]

/cc @pedroigor