Slow or Unreliable RPC Endpoints Causing MetaMask Malfunctions

### What is this about?

Users often experience slow transaction processing or failed transactions. MetaMask should consider providing users with a way to measure RPC performance and recommend more reliable and faster RPCs to improve user experience.

### Scenario

_No response_

### Design

_No response_

### Technical Details

- Implement an RPC health check mechanism within MetaMask

- Display average response times and failure rates of currently selected RPCs

- Provide recommendations for alternative RPCs based on performance

- Offer users an easy way to switch RPCs

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

No implementation files, tests, entry points, or acceptance criteria are named. First clarify the RPC health-check design, performance metrics, recommendation logic, and switching flow with the project stakeholders. Done should include the agreed behavior and validation for measuring RPC reliability and recommending and switching to alternatives.

Written by the indexing model from the issue text.