Enabled hermes JS engine and updated SDK release scripts for both Android and iOS.

* feat(android) set target SDK to 34 and fixed mediaProjection service type

feat(react-native): version 0.72.7 update

* fix(android): refactor immersive mode

feat(settings/native): feature updates

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

Update Android build to support gif
Use GIF format instead of animated webp
Show GIFs in chat messages
Display GIF over tile
Add Giphy button in reactions menu
Added Giphy dialog
Fix isGifMessage to also allow upper case

React Navigation v6.

* feat(security) Security Options screen

Co-authored-by: Saúl Ibarra Corretgé <saghul@jitsi.org>

Introduce navigation for all in-conference screens.

Implements: https://developer.mozilla.org/en-US/docs/Web/API/Performance
Ref: https://github.com/oblador/react-native-performance

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

* feat(share-video) Allow sharing direct video links (mp4 etc) on mobile

* fix linting

* code review

- Fixed react native community slider to work on both android and ios
- Removed InviteButton from native menus
- Fixed buttons spacing in native OverflowMenu
- Participant context menu details are shown only for remote participants

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

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

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

JSC wasn't the cause for the crash we were hunting after all. RN doesn't set
HErmes as the default, neither does Expo, so the jury is still out on Hermes,
and it looks like JSC is still the safest bet.

In addition, the way Hermes is packaged (as a standalone AARs, instead of a
local "Maven repo") complicates the SDK build and can make the resulting build
bloated.

We need to push the Hermes AAR to Maven and have the SDK depend on it.

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.

Will emit new 'network.info' action with the online/offline status and
extra details for native like the network type and
'isConnectionExpensive' flag.

* Adds live streaming sound notification.

* Adds ios resources for the new files.

The naming didn't match, so adjust it. @ cannot be used for maven artifact
names.