Required and optional chains within the same namespace

[pyncz]

Hey! Is there a way to define required AND optional chains within the same namespace on SignClient.connect step?

Now it looks like configs under the same keys in requiredNamespaces and optionalNamespaces are merged in favour of required ones, and the actual checks during the requests are run against it.

For context, we have a dapp that allows to do all sorts of things on one specific chain (that required one), and we are trying to add a bunch of optional ones within the same namespace for bridging.
If there's only required one in the final chains, it doesn't allow requests for other ones; at the same time, if we move those additional chains in requiredNamespaces, then the wallet fails to connect if user doesn't have all of them added in their wallet.