Support ENS resolution on any EVM compatible chain (including L2s)

Nobody has claimed this yet.

### Background
Currently ENS resolution is only supported on Ethereum mainnet. This issue addresses extending support for it for any EVM network supported by ENS.

### Acceptance Criterias
1. User facing functionality for ENS resolution that currently exists for Ethereum Mainnet is replicated for all ENS-supported EVM compatible chains in MM
2. When a network doesn't have ENS support, the `Network does not support ENS` warning is shown when the user tries to input an ENS name on a send flow
3. We should test this with Linea test network (once it has ENS support) and confirm it's working

### Repro Steps
1. Click on Send
2. Input an ENS address such as `Vitalik.eth`
3. See ENS resolved to the correct registered address if you're on Ethereum Mainnet, Goerli or Sepolia or see the `Network does not support ENS` warning if you're on a different network

### References
- Extension issue: https://github.com/MetaMask/metamask-extension/issues/18648
- https://github.com/MetaMask/specifications/issues/11
- https://github.com/MetaMask/metamask-extension/pull/18035
- Dependency: https://github.com/MetaMask/core/issues/1044

Start by reviewing the existing ENS resolution behavior for Ethereum Mainnet, Goerli, and Sepolia, then read the linked extension issue, specifications issue, pull request, and core dependency issue. Done means ENS resolution works across ENS-supported EVM chains, unsupported networks show the specified warning in send flow, and the behavior is confirmed on Linea testnet once supported.

Written by the indexing model from the issue text.