chore: Chore/resolve xcode changes

[Cal-L]

Description

This PR is a chore to clean up Xcode diffs when running yarn setup, which also runs pod install on the main branch.

First, it updates outdated pod checksums in the Podfile.lock
Second, it properly names references in the Xcode project file

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

Example of outdated checksum being automatically updated

Properly named reference

Pre-merge author checklist

• I’ve followed MetaMask 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 passed on Bitrise! ✅✅✅

Commit hash: 0a35afc
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/083580dd-c6ce-42ec-8754-6b0bae6618c3

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

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[NicolasMassart]

I tested it, works fine for xcode files.
Do you know if there's a way to prevent podfile.lock rewrite?
I have this:

[chrisleewilcox]

LGTM

[Cal-L]

I tested it, works fine for xcode files. Do you know if there's a way to prevent podfile.lock rewrite? I have this:

I'll follow up with a way to ensure that the correct pod version is used while running pod install.