chore: Upgrade to React Native 0.74.5

[lorenjohnson]

• Updates from React Native 0.72.12 to latest 0.74.4 (https://react-native-community.github.io/upgrade-helper/?from=0.72.12&to=0.74.4)
• Updates most all dependencies to most recent or otherwise compatible versions

Seems to be all working in peripheral testing, but a deeper pass of testing is a necessity either before or after merge to dev (if we want to save this for part of release QA):

• Blocker for Production builds only: Wait for 0.74.5, or patch: [RN][Hermes] Fore Hermes versions for slices through env var facebook/react-native#45840 / [0.74.4]ERROR: [ContentDelivery.Uploader] Asset validation failed (90360) Missing Info.plist value. A value for the key 'MinimumOSVersion' in bundle XXXX.XXXX/Frameworks/hermes.framework is required. facebook/react-native#45823 (comment)
• Apply patch to react-native-render-html (though works ok with warning): React 0.74 - Update defaultProps to JavaScript default parameters. meliorence/react-native-render-html#661 / https://gist.github.com/awlodarczyk/fab3031d1c05ebf0ebf17444b8f3f532
• Android smoke test
• iOS in depth manual testing
  • Initial Group loads as expected
  • Can change groups
  • Stream
  • Create Post
  • Post Detail
  • Messages / Send Message
  • Receive Push Notification
  • Intercom chat works

---

Adoption (local dev):

• Install Java 17. It is now required for Android builds vs 11 which was the requirement before. This works for that: brew install --cask zulu@17

[thomasgwatson]

lgtm

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11948920	Triggered	Sentry User Auth Token	dd5b886	android/sentry.properties	View secret
11948920	Triggered	Sentry User Auth Token	dd5b886	ios/sentry.properties	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[lorenjohnson]

I have manually tested this on both iOS (Simulator and my phone) and Android in emulation. Everything I have tried, including the list of items above, looks to be working as before and stable. I however will not be surprised if we find a thing or two related to this upgrade as we move forward and implicitly test things as we develop/ our next "release QA". I'm will merge now with that understanding to keep keep things moving, and hoping that is ok.