Registry of Balancer standard contracts (v2)

[EndymionJkb]

Description

Based on #1206, this is designed to be a more straight-forward implementation that still covers all the use cases, but is less error-prone and without troublesome edge cases.

It maintains name => address, and address => info (i.e., state) mappings, but through guaranteeing uniqueness conceptually acts like a single name => address => info data structure, only split to enable querying by either name or address.

These entries are fixed once created (except that isActive can be set to false through deprecation), but it is possible to deregister (delete) a contract, which is the simplest mechanism to fix errors, without complex "replacement" logic.

The "alias" use case is enabled with another mapping, and a single function to add or update an alias. This separates concerns, and prevents possible corruption of the core index (e.g., setting an alias that is the same name as a real contract, which could break things if allowed on the main registry).

Type of change

• Bug fix
• New feature
• Breaking change
• Dependency changes
• Code refactor / cleanup
• Optimization: [ ] gas / [ ] bytecode
• Documentation or wording changes
• Other

Checklist:

• The diff is legible and has no extraneous changes
• Complex code has been commented, including external interfaces
• Tests have 100% code coverage
• The base branch is either main, or there's a description of how to merge

Issue Resolution

[jubeira]

Thanks @EndymionJkb, looks good! I have a few comments / questions, but otherwise LGTM.

Bottom line, I'm trying to simplify the management of the mappings as much as possible (3 feels already too much to me, but I understand it's required to use it in the way it's intended to). That being said, the more we can split the source of truth from the aliases, the better.

[jubeira]

Sorry for being so annoying 😇 but I think there's some room to simplify the code.

[elshan-eth]

Cool!