For single-tenant deployments, this constructor is to be used, as a
full KeycloakDeployment is known at deployment time and won't change
during the application deployment's life cycle.
Pre-installed actions that must be authenticated
Actions include:
CORS Origin Check and Response headers
k_query_bearer_token: Get bearer token from server for Javascripts CORS requests
Login module, which allows to authenticate Keycloak access token in environments, which rely on JAAS
It expects login based on username and password where username doesn't matter and password is keycloak access token.
For single-tenant deployments, it complements KeycloakDeployment
by resolving a relative Auth Server's URL based on the current request
and, if needed, will lazily resolve the Realm's Public Key.