fix: Bitrise android e2e linux builds

[sethkfman]

Description

This PR uses asdf to install node and yarn versions during build setup. Yarn setup was failing due to mismatch of node versions. The root cause was traced down to Bitrise updating the configuration of the linux image used to in the android builds. The specific node version did not have yarn installed by default which cause the yarn setup step to fail.

Related issues

Fixes: NA

Manual testing steps

1. Run this PR using the smoke test E2E workflow and it should pass.

Screenshots/Recordings

NA

Before

Failing E2E: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0501526b-ecd8-447d-b176-d6834586079c

After

Passing E2E in comments below

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/86476392-28b4-44d8-9c8d-1515da174b1d
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[chrisleewilcox]

LGTM