Detox Fixtures Not Consistently Working on Android for MetaMask App on Certain Mac Machines

Nobody has claimed this yet.

### What is this about?

When running Detox tests with fixtures on the MetaMask app for Android, some Mac machines used by dev/QA users encounter issues. While the fixture server starts successfully, the app does not build into the required test state as expected for Android. This issue appears to be intermittent and only affects specific devices.

## Steps to Reproduce
1. Build the app for Android using the command:
`npm run test:e2e:android:debug:build`
2. Run the Detox tests with the command:
`npm run test:e2e:android:debug:run`
3. Observe the app's state after the fixture server starts.

### Expected Behavior
Tests that engage fixtures should start the app in the configured setup where the app opens at a specific spot, similar to the behavior on iOS.

### Actual Behavior
The fixture server runs successfully, but the app's configuration setup is not engaged. Instead, the app starts from the beginning, ignoring the expected fixture configuration.

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [x] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [x] 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 running npm run test:e2e:android:debug:build and npm run test:e2e:android:debug:run on an affected Mac, then trace the Android Detox fixture setup that runs after the fixture server starts. Done means the app opens in the configured fixture state and the Android Detox tests pass consistently on the affected machines.

Written by the indexing model from the issue text.