CI: Add retry logic to prevent builds from failing while installing nvm

[cortisiko]

What is this about?

Some workflows tend to be unstable at random build steps prior to test execution. This is more prevalent on non-main builds (builds that run against feature branches).

For instance:

• The prep_enviroment step would fail sporidically. With this error message:

  Binary download from https://nodejs.org/dist/v20.12.2/node-v20.12.2.tar.xz failed, trying source.

  grep: /Users/vagrant/.nvm/.cache/src/node-v20.12.2/node-v20.12.2.tar.xz: No such file or directory

  Provided file to checksum does not exist.

  Failed to install Node.js 20.12.2

To improve stability, we should add retry logic to the prep_enviroment step to prevent random failures from prematurely causing builds to fail.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

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

[cortisiko]

I'm closing this issue as not done since no action is required on our side. NVM already has built-in retry logic for when the curl command fails.

The main challenge we faced here was that bitrise builds failed while trying to install the node. This appears to be a sporadic issue that occasionally fails due to rate-limiting or throttling. Some have reported similar errors in the NVM repository, as seen here: https://github.com/nvm-sh/nvm/issues/3074. This suggests that the problem originates with NVM and is something others have encountered.