[Reg-1395] Adjust seaport proxy buyer smart contract to support zone interface and allow any order

[Armen-Arakelian]

PR Checklist

Description

Added new workflow for matching marketplace orders - matchOrders. According to recent marketplace logic changes, users now available to create both "sides" orders, meaning to sell domain or to buy domain. If we find 2 fulfilling orders we now can match them from any caller using matchAdvancedOrders function on Seaport core SC. SeaportProxyBuyer acts as a zone in this case, authorazing and validating those orders. It is essential that it contains both functions.

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

[github-actions]

Contracts size report

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

[nickshatilo]

LGTM but would defer to @DeRain for final approval

[DeRain]

Great job! Thank you for fixing linters and prettier.