Add registry attestations to implementation upgrade and module installs

[cpb8010]

As we move forward with vetting modules and providing a store, we should look at adding security to the account upgrade and install process. Compared to clave, our account upgrade process is less secure because we allow anyone to upgrade to any contract individually. We'd want to have a way to check that before you install code, you can see who trusts that code.

This concept of an attestation registry is available via rhinestone's https://erc7579.com/extensions/erc7484 contract. The idea for this is to have a central list of signers for modules, so you can tell who has vetted which contracts. This works equally well for modules as it does for account implementations.

Having the account respect this registry will complicate the install/upgrade process somewhat so we should be sure to have everything we want setup before then!

[cpb8010]

Talking to abstract, they agree on the module registry but disagree on making the account implementation equally user-configurable. My assertion is that module drainers and account drainers are equally malicious, but with account upgrades you could effectively brick the account preventing it from signing any transactions. My objection was who would own this 'blessed' upgrade list, as it could be configured per chain.

This only gets more complicated with DefaultAccount, where it would be upgraded via protocol changes.