chore: Implement retry logic for downloading nvm in Bitrise

[cortisiko]

Description

The purpose of this PR is to add a retry mechanism for downloading nvm to prevent the prep_environment step in bitrise from premature failing which in turn cause a false preception that the e2e tests are flakey. I used wget's --tries and--waitretryoptions to automatically attempt the download up to three times with a five-second wait between retries while downloading nvm.

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

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]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 65354a0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0ac4324d-4223-4fd6-b45f-06f9abf32083

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

[NicolasMassart]

are you sure about the spaces increment additions?

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