Add UUPS support

[Amxx]

Changelog

Core - Internal

• Add a fetchOrDeployProxy that stored new proxies address + type in the manifest
• Update layout to version 3.2: add a list of proxy deployments (address + txHash + kind) to the manifest
• Add a mechanism to extract signatures out of FunctionDefinition (from the AST)
• Add a new error type 'no-public-upgrade-fn'
• Add a list of all public and external function signatures to the validation objects
• Add check for the presence of an upgradeTo(address) function
  • this test is disabled using unsafeAllow: ['no-public-upgrade-fn'] which is automatically added by plugins when operating on a transparent proxy

Plugin - Public

• Add a new field to the DeploymentOptions interface kind which allows users to specify the proxy flavor they want to use. Accepted values are auto (default), uups and transparent.
  • When deploying a new contract, auto fallback to transparent for backward compatibility
  • when upgrading a contract, auto will autodetect the proxy type from the manifest and apply the corresponding checks
• Add warning message when:
  • Deploying a UUPS proxy (that doesn't uses the proxyadmin pattern) while a proxyadmin instance is registered in the manifest.
  • Some proxies are not affected by a proxyAdmin being transfered

Plugin - Internal

• Detect the presence of a proxyAdmin when doing upgrades. This adds support to transparent proxy that are not owned through a proxyAdmin.

[frangio]

Thank you!

Started reviewing the code. Leaving a couple of initial comments, will continue tomorrow.

[Amxx]

This used to be the case, but caused issues during manual tests. I'll have to check that again.

Details: cache of old implementation doesn't contain this field, which caused issues.

[Amxx]

Manual tests look good

[frangio]

cache of old implementation doesn't contain this field

This is solved now because I bumped the validation data version so the cache will be flushed.

[frangio]

I've finished reviewing everything. It looks great.

We need to think about how we want to document this. We can do it in a separate PR.