Request to add Xone Chain (XOC) to MetaMask popular networks

Nobody has claimed this yet.

### What is this about?

As a user, I hope to be able to add Xone Chain through the popular network list when using Matamask, without having to operate through the custom network addition method.

In addition, any media information about Xone Chain in the custom added network cannot be effectively identified. I hope to make preliminary network information confirmation with the Xone Chain Logo.

### Scenario

- Users are able to add Xone network through the add popular network feature;
- No tooltip is shown for Xone in the network list screen of the 'add popular networks' feature;
- The network uses Infura's endpoint as we always want to use rpc endpoints that we know comply to our privacy policy.
- The Infura key should not be revealed to users when users review the details for the Xone network in Settings > Networks.

### Design

- Chain ID: 3721
- Rpc url: https://rpc.xone.org
- Network name: Xone Mainnet
- Ticker: XOC
- Block explorer url: https://xonescan.com/
- Xone Logo: [SVG Resources](https://xone-docs.s3.ap-southeast-1.amazonaws.com/media_kit/Xone_Logo.zip)
- Coin: [SVG Resources](https://xone-docs.s3.ap-southeast-1.amazonaws.com/media_kit/Xone_Coin.zip)

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

- Users are able to add Xone network through the add popular network feature;
- No tooltip is shown for Xone in the network list screen of the 'add popular networks' feature;
- The network uses Infura's endpoint as we always want to use rpc endpoints that we know comply to our privacy policy.
- The Infura key should not be revealed to users when users review the details for the Xone network in Settings > Networks.

### 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_

Start by locating the popular network configuration and the Settings > Networks details view. Verify the Xone Mainnet metadata, chain ID, RPC endpoint, explorer, and logo resources against the acceptance criteria, then run the relevant automation tests and confirm that the Infura key is not exposed.

Written by the indexing model from the issue text.