Scary alerts that are counter-productive.

### What is this about?

MetaMask often displays alerts when interacting with "unknown" addresses, which are quite scary. Often, there is no reason to feel scared, because e.g. the user is actually interacting with long-time deployed and much-used DeFi contract with verified source code etc.

For example, the contract here has Info and Tags added on Etherscan and a total of 176,000 Txs. I would assume that such cross-verification with Etherscan is not only possible, but also highly beneficial. Otherwise, how do we add reputation to make DeFi and UX better and safer?
If MetaMask/Consensys does not want to do it for legal reasons, at least there should be an easy way to inspect the address, instead of having to copy paste it into a blockexplorer.


### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### 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)
- [x] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

The issue names no files, tests, or entry points. Start by locating the alert shown in the attached image and the address-inspection flow, then clarify whether Etherscan verification or an explorer link is intended. Done should be a defined UX change with acceptance criteria and security and product review.

Written by the indexing model from the issue text.