Phantom wallet does not open when MetaMask extension is also installed

[YVeselovskyi]

Describe the bug
When both Phantom and MetaMask browser extensions are installed, clicking on Phantom in the wallet selection modal does not open the Phantom wallet popup. The connection attempt silently fails or gets intercepted by MetaMask's provider.

To Reproduce

1. Install both the Phantom and MetaMask browser extensions in Chrome
2. Go to https://anza-xyz.github.io/wallet-adapter/example/
3. Click "Select Wallet"
4. Choose "Phantom" from the wallet list
5. Phantom wallet popup does not appear — no connection prompt is shown

Expected behavior
The Phantom wallet popup should open and prompt the user to approve the connection, regardless of whether MetaMask is also installed.

Screenshots
N/A — no visible error; the wallet simply does not open.

Desktop (please complete the following information):

• OS: macOS
• Browser: Chrome
• Version: Latest

Smartphone (please complete the following information):
N/A — desktop only

Additional context
This is likely caused by a provider collision. Both Phantom and MetaMask inject into window.ethereum, and Phantom also provides a Solana provider via window.phantom.solana. When MetaMask is present, it may be overwriting or interfering with Phantom's provider detection in the wallet adapter, preventing Phantom from being properly resolved and connected.

[VishantJadhav]

This issue has been open for a bit. Since Phantom recently started injecting into window.ethereum to support EVM, this definitely looks like a classic provider race condition where MetaMask is intercepting the connection.

I'd love to take a swing at fixing this. I'm going to spin up the local environment today and look into two potential routes:

1. Strict scoping to ensure the adapter only resolves window.phantom.solana.
2. Checking if transitioning this specific resolver to use EIP-6963 (Multi-Injected Provider Discovery) is a better long-term fix.