[proposal] update list of managed DIDs and keys based on KMS implementations

[mirceanis]

Based on a commend in #924

In @veramo/kms-web3, the way key metadata is stored by other plugins matters a lot. The key metadata, the controllerKeyId and kid of the key must all align properly for kms-web3 to be able to find the right provider and call it to sign.

Also, if web3 providers change, there should also be some update to the managed DIDs and keys from @veramo/did-manager / @veramo/key-manager.

It is likely that an initialization step is necessary to allow the DIDManager and KeyManager plugins to inspect the KMS implementations for the lists of available keys and then decide to enable/disable their own entries accordingly.