Data type `object` missing as a mandatory supported option for the `value` and `default` operators

[MichaelFraser1999]

The definition for the value and default operators respectively state:

Metadata parameter JSON values:

Mandatory to support: string, number, boolean, array

Operator JSON values:

Mandatory to support: string, number, boolean, array, null

Metadata parameter JSON values:

Mandatory to support: string, number, boolean, array

Operator JSON values:

Mandatory to support: string, number, boolean, array

Whereas all others define object or array of objects as optional to support.

This has been hit as an issue when implementing the OpenID Federation for Wallets standard specifically for the vp_formats_supported metadata which is an object.

While I accept adding this as a mandatory is a breaking change, I think the optional support in value and default should be added. If the authors feel this is better as text in the wallet draft itself, I'm happy to move this issue.

Thanks