chore: pin react-native-tcp to hash

[leotm]

Description

Fix it to the git commit hash we're using (yarn.lock resolved url tar.gz hash),
instead of the latest commit on a contributor's pr branch on the fork (package.json)

i.e. aprock/react-native-tcp@98fbc80
(note: master is few commits ahead)

note: our develop has two more such cases (1, 2)

Related issues

Fixes: variable commit hashes, if the lockfile were to be removed/regenerated

Manual testing steps

Screenshots/Recordings

Before

After

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.

[naugtur]

Please pin all in one go unless we have good reasons not to

[leotm]

Please pin all in one go unless we have good reasons not to

yep this is all #X/head deps on master pinned

(develop is stale last updated ~3y ago, we could do that too in a separate PR if deemed neccessary)

[tommasini]

Can we run the e2e?
LGTM!

[leotm]

Can we run the e2e? LGTM!

thank you ^ just noting added the No E2E Smoke Needed label since the yarn.lock resolved url tar.gz hash remains the same (i.e. it's the same dependency)

[leotm]

github-merge-queue bot removed this pull request from the merge queue] due to no response for status checks (no failed tests) hmm

now audit:ci failing ✘ Audit shows 7 moderate or high severity advisories in the production dependencies on bunch of PRs 🤔
edit: nice work @tommasini getting on it MetaMask/core#5073 #12725

[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 SonarQube Cloud