substrate Name Service Pallet as Collectives Service

This PR expands on what was worked on in https://github.com/paritytech/substrate/pull/11052, getting the name service pallet to a production ready state.

The addition of a register_para and deregister_para will be added, ideally only callable via XCM over OpenGov proposals, as a mechanism for paras to be registered on the service. This will prevent arbitrary / non-existent Para IDs from being stored on the service. The set_address call within the name service resolver can then take a para_id in addition to the address itself, so the service knows which para to route addresses to.

[x] Fix up code from #11052 to work with master and get tests working.
[x] Review of pallet and write-up high level lib doc.
- [x] Check deposit mechanism and whether deposits should be added to subdomains too (they are).
- [x] Update header comments to match master.
- [x] Registrations storage item to have counter.
[x] Add register_para and deregister_para calls to store Para IDs that wish to be a part of the name service.
- [x] Use RegistrationManager and ensure origin is RuntimeOrigin for these calls.
- [x] Provide a suffix that acts as the source of truth for the para.
[x] set_address to also require para_id arg, ensure para id is registered.
[x] Revise configs and move to storage where applicable (deposits, tiers) via a set_configs call (similar to Nomination Pools set_configs) for root origin to manage.
[x] Make suffixes unique, reverse lookup & set address to take suffix instead of para ID.
- [x] hash -> address, suffix -> para.
[x] Remove controller related code in preparation for a NameService Collectives proxy type.
[x] Expand call comments.
[x] Don't unreserve deposit on reveal. Instead, assign to owner (if depositor different) to back up registration and incentivise deregistering.
[x] Write up benchmarks and plug in call weights.
[x] Expand pallet docs with calls.
[x] Fix tests to account for domains & configs.
[x] Use domain terminology for para registrations, and name terminology for nodes.
[x] Revisit tests and determine what needs to be added.
[x] Add test proving that a tree of a registered TLD and subnodes can all be deregistered and removed from storage.
[x] Bound renew max length & update benchmark.
[ ] Cumulus Companion (Westend Collectives only): Add pallet to runtime and add a NameService proxy to have access to resolver management and registration of new subdomains.

Other tasks post initial release

Explore whether a force_deregister_para is possible, to asynchronously query Relay Chain and remove para from name service if the para is no longer registered.
Decentralised / trustless transfer of ownership on-chain process.

Jul 02 '23 14:07 rossbulat

bot clean

Jul 04 '23 11:07 rossbulat

bot rebase

Jul 06 '23 10:07 rossbulat

Rebased

Jul 06 '23 10:07 paritytech-processbot[bot]

bot rebase

Jul 07 '23 16:07 rossbulat

Rebased

Jul 07 '23 16:07 paritytech-processbot[bot]

bot rebase

Jul 08 '23 12:07 rossbulat

Branch is already up-to-date

Jul 08 '23 12:07 paritytech-processbot[bot]

bot rebase

Jul 10 '23 17:07 rossbulat

Rebased

Jul 10 '23 17:07 paritytech-processbot[bot]

bot rebase

Jul 14 '23 07:07 rossbulat

Branch is already up-to-date

Jul 14 '23 07:07 paritytech-processbot[bot]

bot bench $ pallet dev pallet_name_service

Jul 14 '23 12:07 rossbulat

@rossbulat "$PIPELINE_SCRIPTS_DIR/commands/bench/bench.sh" pallet dev pallet_name_service (https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3188692) was cancelled in https://github.com/paritytech/substrate/pull/14491#issuecomment-1635801559