chore: cicd e2e hardening

[jake-perkins]

Description

Handle scenarios where MQ and PR context is different when executing in the merge queue context

Related issues

Fixes:
The E2E Bitrise status from not being in a completed state when in the MQ

Manual testing steps

Tested in alternate repo replicating setup
https://github.com/MetaMask/temp-gh-action-testing/actions/runs/12169779361/job/33943429158

Screenshots/Recordings

Before

N/A CICD Only

After

N/A CICD Only

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 66adda5
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1ca83a57-106a-4781-90e8-20733befcbc8

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Cal-L]

LGTM