[REG-1332] feat: move uns tlds minting config outside of minting manager

[roman-gnativ]

PR Checklist

Linear ticket:
https://linear.app/unstoppable-domains/issue/REG-1332/introduce-tld-configs-in-uns-repo

Background:
To deploy our registry contracts to the base chain, we have made UNS contracts unified across chains, which, in the case of the base chain, means removing the TLD config outside the minting manager contract.

What was done:

• Tld config removed from the Minting manager smart contract
• Tld config introduced in the uns repo
• Added a deployment task that mints all TLDs from the TLD config

1. Contracts versioning

• Make sure that the patch version of the contracts is increased if changes have been made to the UNSRegistry, MintingManager, ProxyReader, ENSCustody contracts.
• Make sure that the minor version of the contracts is increased if breaking changes have been made to the UNSRegistry, MintingManager, ProxyReader, ENSCustody contracts. It includes changes of interfaces.

2. Contracts licensing

• Make sure that no SPDX-License-Identifier defined in contracts.
• Make sure that the header is added to the new contract files.

  // @author Unstoppable Domains, Inc.
  // @date {Month} {Day}(ordinal), {Year}
  

3. Coverage

• Make sure that the coverage of contracts has not decreased and strive 100%

4. Configs versioning

• Make sure that the version of uns-config.json is increased if changes have been made to the config.
• Make sure that the version of ens-config.json is increased if changes have been made to the config.
• Make sure that the version of resolver-keys.json is increased if changes have been made to the config.
• Make sure that the version of ens-resolver-keys.json is increased if changes have been made to the config.

5. Package versioning

• Make sure that the patch version of package is increased if valuable changes have been made to the package. It includes contracts update, configs update, etc.
• Make sure that the major.minor version of package is synced with version of UNSRegistry contract.
• Make sure that the CHANGELOG is updated with short description for the new version.

6. Code review

• resolver-keys.json code review is required from DevTools team
• ens-resolver-keys.json code review is required from DevTools team
• For all other changes code review is required from Registry team

[nickshatilo]

overall LGTM @roman-gnativ, just a few naming / structure suggestions

[nickshatilo]

please increase version of ens-config

[nickshatilo]

same here

[github-actions]

Contracts size report

Contract name	Size (KiB)	Delta (KiB)
ENSCustody	13.063	0
MintingManager	18.92	-1.136
ProxyReader	15.176	0
UNSRegistry	20.725	0