re-add an option to use format/type in authorization_details

[Sakurann]

documenting for visibility.

On Jan-18-2024 WG call, @tlodderstedt brought up an issue that the change made in #137 mandates the wallet to know credential_configuration_id, which takes away the advantage of RAR over scopes approach.

Discussed in the WG and agreed to re-add the option to use format/type in authorization_details in addition to an option to use `credential_configuration_id for the following reasons:

• there are implementers that are using out-of-band mechanisms instead of the credential issuer metadata as defined in the spec. or implementers that want to use metadata only to communicate the endpoint and display and not the credential format/type. (needs another issue if credential_configurations_supported should be optional)
• we may end up keeping only credential_configuration_id, but right not there is not enough implementation experience and keeping only one option would limit flexibility
• current implementations that implement credential_configuration_id in RAR would not be affected.
• AS that supports RAR will have to make a decision whether to support both format and id or one of those approaches (cc @pmhsfelix )