Remove faulty Out of Memory detection

[matux]

Description of the change

There is no way to deterministically know if a crash occurred due to an out of memory error in iOS.

The current implementation uses some fuzzy logic to achieve this, but the false positives overweight the good:

1. Out of memory crashes are a very rare occurrence in iOS.
2. We pretty much report that every crash "could" be due to OOM.
3. The first time an app is installed and run, the code believes it crashed due to an OOM.

Trying to detect this is a bad practice that's been dropped industry, and no crash reporting service has it as a feature simply because the OS will never report whether some crash is due to OOM.

Therefore, I'm removing this logic, and thus removing a large amount of complexity out of the codebase.

• This PR also fixes some broken tests that haven't been working for some time now.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Maintenance
• New release

Related issues

• 119951

Checklists

Development

• Lint rules pass locally
• The code changed/added as part of this pull request has been covered with tests
• All tests related to the changed code pass in development

Code review

• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
• "Ready for review" label attached to the PR and reviewers assigned
• Issue from task tracker has a link to this pull request
• Changes have been reviewed by at least one other engineer