Identify Sentry Related Logs for Users

### What is this about?

This ticket will identify and design a user error notification pattern for Sentry information that should be logged to the user and not the error logging system.

#### Errors suggested to be shown to the user

These errors can come from different parts of the application.

-

#### error notification pattern suggestion
- existing toast message component (see comment https://github.com/MetaMask/metamask-mobile/issues/14683#issuecomment-2851407915)
- new ui (reach out to @yanrong-chen )

### 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)
- [x] 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

_No response_

Review the existing toast message component and the issue comment linked in the body; no source files or tests are named. Clarify which Sentry errors belong in user notifications, agree on the proposed UI with design, product, and engineering, and define acceptance criteria for the completed notification pattern.

Written by the indexing model from the issue text.