Select the client-registration approach for an authorization server,
following the spec priority order:
1. pre-registered client information, if available;
2. Client ID Metadata Documents, if the AS advertises support
(client_id_metadata_document_supported) and a valid HTTPS-URL
client_id is configured;
3. Dynamic Client Registration, if the AS exposes a registration_endpoint;
4. otherwise prompt the user.
havePreRegistered is true when the caller already holds a client_id for
this AS; clientIdMetadataUrl is the configured CIMD URL (empty if none).
Select the client-registration approach for an authorization server, following the spec priority order: 1. pre-registered client information, if available; 2. Client ID Metadata Documents, if the AS advertises support (client_id_metadata_document_supported) and a valid HTTPS-URL client_id is configured; 3. Dynamic Client Registration, if the AS exposes a registration_endpoint; 4. otherwise prompt the user.
havePreRegistered is true when the caller already holds a client_id for this AS; clientIdMetadataUrl is the configured CIMD URL (empty if none).