RN 0.76 will be doing this change, so let's get ahead.

THis puts the iPhione 6S as the baseline model, which was released in
September 2015.

* deps(react-native): updates regarding to 0.73.8

* chore(deps, react-native): changes regarding react native update to 0.72.14

- Update project files
- Make sure CI uses Xcode 15.2
- Fix custom Xcode build scripts to depend on the Info.plist file
  generation
- Combine 2 scripts related to Firebase into a single one

feat(rn, ios): build fixes and metro-config updates

feat(react-native): version 0.72.7 update

* feat(rn): update to 0.70.14 and removed libray_search_paths variables from ios project

* feat(deps,rn) update React Native to version 0.69

This (partially) reverts commit ddab27e292.

We're reverting this to fix the iOS 16 layout problems caused by the interaction between the app rootViewControoler and JitsiMeetViewController, with the downside that using any RN components based on native view controllers will most likely be faulty. The solution for this would be to change the SDK's entry point to a view controller, instead of JitsiMeetView.

Bitcode is no longer supported, so remove it. The M106 WebRTC version no
longer contains bitcode either, but it embeds dSYMs.

We need it for the RN module since it won't be (re)generated. It has not
changed in 4 years, so I guess it's safe to assume it'll stay that way.

Fixes: https://github.com/jitsi/jitsi-meet/issues/11188

Backport of: a1c445a39c

Also update native dependencies.

This is what upstream RN does now.

I'm updating to RN 0.63 instead of the latest (0.66 at the time of this writing)
so we can update the navigation related libraries to their latest versions, and
then proceed with the larger leap towards the latest RN.

- Remove unicode charcters from filenames
- Simplify code for copying them to the iOS SDK

Amplitude has gone back to having a separate package for RN, so switch to it.

The Jitsi team would like to thank @AliKarpuzoglu, @linuxpi and The Hopp Foundation for the initial effort and help throughout.

feat(external_api) exposes more events from JS to native and adds the ability to send actions from native to JS.

The amplitude-js library gained React Native support so there is no need to keep
separate implementations.

Swift has a longstanding bug where a framework and a type cannot be named the
same. We have somehow managed to not run into this, but it now seems to be
hitting us.

Since this is a breaking change, this starts the road for SDK 3.0.

Supersedes: https://github.com/jitsi/jitsi-meet/pull/4818
Fixes: https://github.com/jitsi/jitsi-meet/issues/4812

We are downloading code off the Internet and executing it on the user's device,
so run it sandboxed to avoid potential bad actors.

Since it's impossible to eval() safely in JS and React Native doesn't offer
something akin to Node's vm module, here we are rolling our own.

On Android it uses the Duktape JavaScript engine and on iOS the builtin
JavaScriptCore engine. The extra JS engine is *only* used for evaluating the
downloaded code and returning a JSON string which is then passed back to RN.

These provide the ability to integrate the SDK with some other application
loggers.

At the time this was written we use Timber on Android and CocoaLumberjack on iOS.

In addition to the integration capabilities, a LogBridge React Native module
provides log transports for JavaScript code, thus centralizing all logs on the
native loggers.

This commit refactors device selection (more heavily on iOS) to make it
consistent across platforms.

Due to its complexity I couldn't break out each step into separate commits,
apologies to the reviewer.

Changes made to device handling:

- speaker is always the default, regardless of the mode
- "Phone" shows as a selectable option, even in video call mode
- "Phone" is not displayed when wired headphones are present
- Shared device picker between iOS and Android
- Runtime device updates while the picker is open

* Adds live streaming sound notification.

* Adds ios resources for the new files.

At the moment it includes:

- display name
- email
- avatar URL

This information is used *only* if no token was specified.

They may contain sensitive information.