redirect_uri and client_id for x509_san with DC API

[TimoGlastra]

When using DC API with x509_san_dns, should the requirements around redirect_uri/response_uri just be dropped since there is no redirect_uri/response?

If the Wallet can establish trust in the Client Identifier authenticated through the certificate, e.g. because the Client Identifier is contained in a list of trusted Client Identifiers, it may allow the client to freely choose the redirect_uri value. If not, the FQDN of the redirect_uri value MUST match the Client Identifier without the prefix x509_san_dns: