chore: clarify the events and cleanup the list to align with extension

### What is this about?

clarify the events and cleanup the list to align with extension (when possible as some events don't exist on both platforms)

see Segment tracking plan for Mobile

### Scenario

_No response_

### Design

_No response_

### Technical Details

- Check with feature PMs what events should be preserved, updated or removed

### Threat Modelling Framework

_No response_

### Acceptance Criteria

- Tracking schema updated
- No unreviewed event left

### Stakeholder review needed before the work gets merged

- [ ] 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

- https://github.com/Consensys/segment-schema/blob/main/tracking-plans/metamask-mobile.yaml

Start with the referenced metamask-mobile.yaml tracking plan and compare its mobile events with the extension event list. Check with the relevant feature PMs which events should be preserved, updated, or removed. Done means the tracking schema is updated and no event remains unreviewed.

Written by the indexing model from the issue text.