chore: Enable linting Pods and re-organize setup.mjs file

[Cal-L]

Description

This PR refactors setup.mjs file with the purpose of:

1. Moves Gemfile into iOS directory, which is where it belongs since it only relates to iOS. We also updated everywhere that calls bundle install or exec so it's calling it in the ios directory
2. Run pod install in CI for detecting diffs in Podfile.lock

Because we're now running pod install in the CI, the total ci.yml job time will take longer. However, it still completes before some other tasks such as unit tests. And since it runs in parallel to those, we should not see an increase in total CI run time.

Related issues

• Enable pod diffs in Github CI #11293
• chore(ci): lint Podfile.lock #9789

Manual testing steps

• Running yarn setup still works normally when run locally
• CI passes when run
• CI fails when Podfile.lock is changed when pod install runs in the CI

Screenshots/Recordings

Before

After

Example of pod file diff detected
https://github.com/MetaMask/metamask-mobile/actions/runs/10746121351/job/29806449687?pr=10880

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: c930d80
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d74ea28e-fb3a-4a4e-9283-1d0b03ff4bdc

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: fc6238f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2a25edc8-6da8-4566-8aec-8711ffdd6de1

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: eced61a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5a15195b-7889-4b61-b936-1c689e96f2df

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

[sonarqubecloud]

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