fix: bump restore cache step in Bitrise

[vinistevam]

Description

This PR aims to fix an issue where restore-cache steps in Bitrise where getting stuck and breaking pipelines.

After some investigation the latest version of the step restore-cache fixes an issue with the retry mechanism when a chunk (part) download fails the step will retry the download of that specific chunk. Preventing the step from getting stuck.

Additionally taking the opportunity to update all the restore steps to version 2 which includes multithread download, which might save us some seconds in each run.

Related issues

Fixes: #8360

Manual testing steps

1. Run smoke and regression tests

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• 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.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f13f7788-ff1a-46fa-9afd-7e575e990433
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[vinistevam]

Regression tests: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/09975e03-96d2-406b-b8eb-3f0c75d939f8

[github-actions]

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a38c1bff-654e-46e1-b807-e6731eec17a8
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1a44cb3) 40.40% compared to head (1137722) 40.40%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8384   +/-   ##
=======================================
  Coverage   40.40%   40.40%           
=======================================
  Files        1240     1240           
  Lines       29993    29993           
  Branches     2878     2878           
=======================================
  Hits        12120    12120           
  Misses      17175    17175           
  Partials      698      698           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[NicolasMassart]

Looks good to me.

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud