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

If the readyToClose event was fired there is no need to "leave" the
meeting, it just circles back to the app unnecessarily, potentially
creating another readyToClose event.

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

We need to pass the Activity to get back to in the intent, but since we
launch the notification from a Service things got a bit more involved.

* feat(android/sdk): for API >= 33, launch JitsiOngoingConferenceService
only if POST_NOTIFICATIONS and RECORD_AUDIO permissions have been granted

* feat(android/sdk): create setConfigOverride for array list of objects

* feat(android): list post notifications permission

* feat(toolbox/native): custom buttons for the OverflowMenu

* feat(subtitles): created separate helpers for delegating transcription chunks events 
on web and mobile

* react-native-sdk(android): removed related modules, services to screen-share feature and updated peerDeps

* feat(android): media projection is now done through react native webrtc

* feat(android): update media projection notification build

* feat(android): separate MediaProjection and OngoingConference notifications

* feat(android): fixed screen sharing for Android 33

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

feat(react-native): version 0.72.7 update

* (react-native-sdk) Adds `CONFERENCE_FOCUSED` and `CONFERENCE_BLURRED` events to the external and RN API

* fix(android): refactor immersive mode

* sdk(android): rework events and variables inside modules to not depend on our instance manager holder

This basically reverts
e61ccc956f
since we are no longer interested in using Detox.

In addition, the WebRTC initialization code was only placed in the RAN
instance manager holder's App initialization path, which is now gone, so
add it to the Activity initialization path.

When we refactored the external API to use broadcast actions leave() was
changes to use the hangup broadcast action.

This mechanism does not seem to work while onDestroy is getting
executed, however.

There is another way to accomplish the same, for the particular case of
hangup: to pass empty props to the running RN application. This was the
previous behavior too.

This PR introduces a new abort() method on JitsiMeetView, which does
exactly that, passes empty props to RN. This allows cleanup to happen
and the meeting properly ends when the activity is swipped from the
recents list.

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

Adapt to changes in the Android plugin initialization.

Leverage the new module initialization to simplify enabling WebRTC
logging.

chore(deps): updated rn-gesture-handler

This commit allow to override integer configuration like this one:

JitsiMeetConferenceOptions options =
    new JitsiMeetConferenceOptions.Builder()
    .setConfigOverride("resolution", 1080)
    .build();

This requires a custom video encoder / decoder factory which uses the
hardware codec only for H.264 and the software implementations for the rest.

Activity.registerActivityLifecycleCallbacks is only available in API level 29.

Ref: https://developer.android.com/reference/android/app/Activity.html#registerActivityLifecycleCallbacks(android.app.Application.ActivityLifecycleCallbacks)