Include cCOP in Token Autodetection Function

### What is this about?

Please include the cCOP token in the autodetection function.
Blockchain: Celo
- Token Name: Celo Colombian Peso
- Token Ticker: cCOP
- Contract Address: 0x8a567e2ae79ca692bd748ab832081c45de4041ea
- Issuer: https://www.mentolabs.xyz/
- Source Of Verification: https://reserve.mento.org/
- Logo:

### Scenario

It should be included in autodetect function, because Celo Colombia is onboarding people into Crypto using this StableCoin pegged to the Colombian PeSo price, is a local stablecoin.
People that is using this coin are newbies to web3 , importing a Contract is quite a barrier for them, so it would be great if we can include this token in the Autodetect function of Metamask.

### Design


### Technical Details

- Contract Address: 0x8a567e2ae79ca692bd748ab832081c45de4041ea
- Ticker: cCOP
- Name: Celo Colombian Peso

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [x] Engineering (needed in most cases)
- [ ] Design
- [x] 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

- Issuer: https://www.mentolabs.xyz/
- Source Of Verification: https://reserve.mento.org/

No source file or test is identified in the issue. Start by locating the existing token autodetection entry point and comparable Celo token registrations, then verify that cCOP is detected with the provided contract address, ticker, and name.

Written by the indexing model from the issue text.