Alternative fix for the TransparentUpgradeableProxy "decoding" bug

[Amxx]

Partly revert and replace #4154.

This alternative fix is motivated by the goal to make more localized changes, since #4154 is a larger refactor.

Since the first commit in this PR is a revert of 5523c14 (#4154), it's better to see the diff against its parent.

[changeset-bot]

⚠️ No Changeset found

Latest commit: fae9f5a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ernestognw]

I reviewed this alternative with Seppi and his main concern was related to extensibility. I don't think we should expect issues with overriding (agree they shouldn't be frequent and not recommended), but any modification to this contract will face the issue of needing to mine a clashing selector.

I share the same concern for legitimate possible use cases.

[frangio]

any modification to this contract will face the issue of needing to mine a clashing selector.

In my view, this is not something that is introduced by this PR, it's just implied by the transparency requirement.

The alternative is #4154, which makes extending the proxy a little more cumbersome.

[frangio]

I've updated the docs a little, with a focus on how they appear in the site.

[frangio]

We've decided to keep the fix from #4154.

Moved the docs improvements to its own PR: #4181