[chore] Upgrades to yarn 4 and points to latest node 18

[FrederickEngelhardt]

Description

Significantly faster installation of the project. Modernized dependency tools etc leveraging [email protected]

Questions

• Is there any known reason / risk to this [email protected] upgrade? Outside of pipeline fixes for auto builds
• Any reason to be on node 18.18.0? Node 18.20.4 contained a few fixes to jest specifically that unblocked runtime issues with jest + latest version ships corepack, but 18.18 did not expose this.

TODOS

• This PR has not fixed pipeline automation for [email protected]. I'm not sure I'll be able to test the fixes via this PR (for external fork permissions). But I can look at any actions that are available and attempt to add [email protected] compatibility.
• If PR Add corepack compatibility for v1 yarn...yarn@1 still is super slow #3607 is accepted instead or before this PR, this current PR will need to remove the yarn 1 copy within .yarn/releases/.

Checklist

• I've read CONTRIBUTING.md
• I updated the doc/other generated code with running yarn generate in the root folder
• I have tested the new feature on /example app.
  • In V11 mode/ios
  • In New Architecture mode/ios
  • In V11 mode/android
  • In New Architecture mode/android
• I added/updated a sample - if a new feature was implemented (/example)

Screenshot OR Video

Component to reproduce the issue you're fixing

[mfazekas]

Questions

• Is there any known reason / risk to this [email protected] upgrade? Outside of pipeline fixes for auto builds
  It's fine to upgrade to later yarn if CI and example on local works

• Any reason to be on node 18.18.0? Node 18.20.4 contained a few fixes to jest specifically that unblocked runtime issues with jest + latest version ships corepack, but 18.18 did not expose this.
  Node 18.18 was the latest LTS when, changed it. I think we can also upgrade to node 20

[mfazekas]

pr needs fixing in ci