[Bug]: Network Requests - RPC requests for `eth_blocknumber` sent to the 3 different RPC providers I had for the same network

### Describe the bug

I had 3 different RPC providers for Sepolia. After loging out (and having Sepolia selected) I could see requests for `eth_blocknumber` being sent to the 3 providers, for the same network (Sepolia).
Still unclear how this happened or which feature caused this.

Update - I could reproduce the same wiht Arbitrum Sepolia providers. Requests are sent to my 2 providers, for that same network.

### Expected behavior

_No response_

### Screenshots/Recordings

https://github.com/user-attachments/assets/b51bd5d6-2b10-4e2a-8a9b-e009bbae985e

https://github.com/user-attachments/assets/ea607cfe-9d71-4372-b449-7ae7bd38d0d5

### Steps to reproduce
1. Import this RPC `sepolia-rollup.arbitrum.io/rpc`
2. Import this RPC `arbitrum-sepolia-rpc.publicnode.com`
3. Switch networks and providers a couple of times
4. Check network requests

### Error messages or log output

```shell

```

### Detection stage

On main branch + in prod

### Version

until not having repro steps, cannot identify in which version is appearing. I found it in main

### Build type

None

### Browser

Chrome

### Operating system

Linux

### Hardware wallet

_No response_

### Additional context

_No response_

### Severity

_No response_

Start by reproducing the issue with the two Arbitrum Sepolia RPC URLs in the listed steps, then inspect the network requests after switching networks and providers. Trace which provider-selection or request-dispatch path sends eth_blocknumber requests; done when the cause is identified and requests no longer go to multiple providers for the same network.

Written by the indexing model from the issue text.