Rotate key management to multi-sig

[sisyphusSmiling]

Description

Currently, there is a single 1000.0 weight key active on the hybrid custody deployment account that is managed via Google Cloud KMS. Per the deployment account management proposal, this key should be rotated out in favor of multi-sig management.

TODO

• [ ] Retrieve asymmetric signing key info from key holders, managed via GCP KMS
  • [x] @austinkline
  • [x] @bluesign
  • [ ] @an1va
  • [x] @jacob-tucker
  • [X] @bjartek
  • [X] @lmcmz
  • [x] @rrrkren (pending KMS resource ID)
  • [X] @sisyphusSmiling
• [x] Add all keys to deployment account at 250.0 weight
• [ ] Dry run added keys with hello.cdc
• [ ] Revoke currently active 1000 weight key from deployment account

[sisyphusSmiling]

Update, we added all keys to a testnet dry run account 0x3027cc0f80bdf2ff with successful dry run transactions (first and second).

Due to time constraints, we'll coordinate another time to achieve quorum on the hybrid custody mainnet account.

[sisyphusSmiling]

Keys have been added to the mainnet account 0xd8a7e05a7ac670c0

Full weight key at index 0 should be revoked once all other partial weight signers have been included in a successful dry run.