Multichain explorer v2

[tom2drum]

Description and Related Issue(s)

This PR delivers Multichain explorer V2 improvements: aggregated address data per chain, search redirect behavior, creator / implementation on the contract tab, chain layout and ranking, ENS domains on the address view, and custom token types (e.g. ZRC-2) support.

Proposed Changes

• Aggregated info per chain (Resolves [Multichain] Aggregated info card per chain #3170): Address page shows data per chain with chain cards, portfolio net worth, and token list with chain filter.
• Search redirect (Resolves [Multichain] Support redirect to a correct view from search #3145): Navigating to a search result (e.g. from “show all results”) no longer triggers an unwanted redirect; correct view is shown.
• Creator & Implementation (Resolves [Multichain] Add implementation mention for proxy contracts #3255): Contract tab on the multichain explorer shows Creator and Implementation (for minimal proxies, EIP-7702) with links, matching single-chain behavior.
• Chains layout & ranking (Resolves [Multichain] Supported chains new layout and ranking #3171): New chain widget design on home, chain select with filter, ecosystems page and navigation, mobile-friendly chain widget styles.
• ENS on address (Resolves [Multichain] Support multiple ENS protocols on multichain #3070): Address domains (ENS) displayed on the multichain address view; lazy-loaded.
• Custom token types (Resolves [Multichain] Support custom token types #3256): Extensible token types (e.g. ZRC-2 for Zilliqa) in multichain; getTokenTypes signature updated, token type filter and display adjusted.

No changes to environment variables in this PR.

Additional info

I will rename all occurrences of "Op Superchain" in the codebase to "Multichain" in the following PR.

Checklist for PR author

• I have tested these changes locally.
• I added tests to cover any new functionality, following this guide
• Whenever I fix a bug, I include a regression test to ensure that the bug does not reappear silently.
• If I have added a feature or functionality that is not privacy-compliant (e.g., tracking, analytics, third-party services), I have disabled it for private mode.
• If I have added, changed, renamed, or removed an environment variable
  • I updated the list of environment variables in the documentation
  • I made the necessary changes to the validator script according to the guide
  • I added "ENVs" label to this pull request