Suggestion to provide explicit getter for registry.proxies

[razgraf]

The v4.0.0-beta.5 update replaced the proxy mapping accessor. What used to be a dedicated getProxy method has now been replaced by an auto-generated getter called proxies.

I'd suggest reverting back to an explicit getProxy (or proxyOf) method.

While the name of the variable is still contextually correct, when used as a getter it implies plurality. When queried/read, the contract interface should make it clear that a user holds a single proxy not multiple proxies.

Example of the API as shown on Etherscan

[PaulRBerg]

Yep; fully agree that getProxy is clearer, and that the extra getter is worth it.

Let's wait for the audit to finish, and I will try to include this in the post-audit changes.

[PaulRBerg]

Implemented via #118.