Identify inconsistencies between Mixpanel and Sentry vault corruption reporting

### What is this about?

The numbers that we see between what we consider vault recovery are significantly different between Sentry and Mixpanel. While there will be some level of discrepancies, we will want to better understand where these discrepancies are coming from. For example, should we see a mixpanel event for every sentry event related to vault recovery? Mixpanel currently shows us lower numbers than Sentry even though Sentry is sampled. We will want to create a flow chart illustrating the possible scenarios that leads to the errors that we're seeing to better understand what users are experiencing

### Scenario

_No response_

### Design

_No response_

### Technical Details

- Create flow chart here - https://www.figma.com/design/dFKcuZ5dUkZKzWg0xReC6I/Mobile-Flow-Charts?node-id=151637-473
- Illustrate the possible scenarios that lead to vault recovery
- Include places where Sentry and mixpanel are being logged (vault recovery events)

### Threat Modeling Framework

_No response_

### Acceptance Criteria

- Flow chart should illustrate all of the scenarios and events and it should be easy to follow

### Stakeholder review needed before the work gets merged

- [ ] 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 by reviewing the vault recovery flow and the Sentry and Mixpanel event points, then use the linked Mobile Flow Charts Figma file as the destination. Map every reported recovery scenario and indicate where each event is logged; done means the flow chart covers all scenarios and events and is easy to follow.

Written by the indexing model from the issue text.