Use proxies from OpenZeppelin Contracts 4.8.3

[ericglau]

Closes #774
Closes #773
Closes #772
Closes #771

Updates proxies in order to use updated TransparentUpgradeableProxy from OpenZeppelin Contracts 4.8.3.

Note: Using this version of the plugin to verify a proxy that was deployed by a previous version of the plugin will fail. See #674 for details. Users who are affected should downgrade the plugins to the previous version, run the verify task, then upgrade the plugins back to the latest version.

[socket-security]

New dependency changes detected. Learn more about Socket for GitHub ↗︎

---

👍 No new dependency issues detected in pull request

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

Pull request alert summary

Issue	Status
Install scripts	✅ 0 issues
Native code	✅ 0 issues
Bin script shell injection	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues

---

📊 Modified Dependency Overview:

⬆️ Updated Package	Version Diff	Added Capability Access	+/- Transitive Count	Publisher
@openzeppelin/contracts@4.8.3	4.1.0...4.8.3	None	+0/-0	frangio
@openzeppelin/contracts-upgradeable@4.8.3	4.1.0...4.8.3	None	+0/-0	frangio

[frangio]

Is there a reason for this change?

[frangio]

Oh, I remember now, and I understand why this was done.

[ericglau]

Commenting for completeness:

The upgradeProxy function in the plugins invokes the upgradeToAndCall or upgradeTo function on the proxy, regardless of whether it is a UUPS or Transparent proxy. It did this by using TransparentUpgradeableProxy's contract factory to encode those functions, which depends on the ABI. (Note this also works for UUPS proxies because those function signatures are the same between UUPS and Transparent).

In OpenZeppelin Contracts 4.8.3, the upgradeToAndCall and upgradeTo functions are not part of TransparentUpgradeableProxy's ABI, but are in the interface ITransparentUpgradeableProxy's ABI. Therefore, we use ITransparentUpgradeableProxy's contract factory to encode those functions instead.

[frangio]

LGTM