[EPIC] Eliminate [100]% of Sentry issues with more than 100K occurrences over the last 30 days (current: 13). Shown through a declining of issues 30, 14, 7 and 0 days.

### What is this about?

Sentry is the tool we use for error monitoring in production. In theory, it is meant to inform us about new unexpected issues, but in practice, it is currently polluted by a significant number of issues, many of which are false positives (i.e., either not new or not unexpected). We should clean the way some of our errors are thrown in the Mobile app to reduce the number of false positives, either by better grouping issues that need to be grouped or by moving certain issues to our analytics system (Segment) instead of Sentry when they are not unexpected. True positives should be fixed.

The two main benefits of cleaning these issues up are that it will help teams troubleshoot issues faster by reducing noise from false positives, and it will reduce the cost of Sentry, which depends on the number of issues.

[Sentry Report Reference](https://metamask.sentry.io/issues/?environment=production&project=2299799&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-list&sort=freq&statsPeriod=30d&viewId=157225)

### Scenario

_No response_

### Design

_No response_

### Technical Details

- Review top 30 issues
- Identify issues already address in current release and resolve
- Identify issues that are logged incorrectly
- Identify issues that should be metrics events
- Identify issues that should be user notifications

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [x] 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 with the linked Sentry report and review the top 30 production issues from the last 30 days. For each, check whether it is already addressed in the current release, logged incorrectly, better represented as a Segment metric, or should notify users. Done means the issues are appropriately fixed, regrouped, moved, or resolved so the tracked high-volume issue count declines to zero.

Written by the indexing model from the issue text.