Expand ENS TokenScope Coverage

[lightwalker-eth]

• Explore adding support for Seaport 1.6
• Explore adding support for additional chains where Seaport is deployed.
• Explore adding support for WETH
  • Validate the multichain ERC20 contract addresses for all supported currencies
• Explore removing the orderHash field from our exposed data model. It's seems to be the only seaport-specific detail we're currently exploring. Cautious about introducing this.
  • Or perhaps we add to ENSDb but explicitly note how we should not expose this field in APIs (for now) for the reason cited above.
• Explore constraining (explicitly) our support for ERC1155: constrain our support only for cases where a single token for a particular name exists.
• Increase strict correctness of determining currencyIds. See: Feat/tokenscope #970 (comment)
  • Related: Refactor lib/currencies.ts #984
• Consider additional rules / logic for ConsiderationItem.recipient
• Consider normalizing data models with the name_sales table, such that name_sales makes foreign key relationships to name_tokens.
  • All sales are associated with an indexed token that is actively minted at the time of the sale
• Consider adding an indexed table that is a historical log of all NFT transfers
  • Or perhaps better: create a token_activity table that logs all forms of activity of an NFT -- including both transfers and sales (which are a subset of transfers)
• Add foreign keys to data model