React Navigation v6.

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.

* feat(security) Security Options screen

This event is the event host applications need to listen to for knowing when to
dispose the SDK from now on.

Since the introduction of breakout rooms it's possible that we navigate from one
meeting to another, so there will be several conference join / terminations.

In addition, local track destruction is now moved to SET_ROOM when there is no
room, aka, we are going back to the welcome page or to the black page.

It got replaced by a feature flag.

It has been non-functional for a while.

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

Introduce navigation for all in-conference screens.

It has to be an application context.

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

YOLO.

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

Allows for overriding any (overridable, of course) config option.

* 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

Check whether context is that of an Activity before launching the Jitsi Conference Activity. If context is not an activity context, apply flag FLAG_ACTIVITY_NEW_TASK to the Jitsi Activity Intent to ensure activity can launch without error.

This scenario would manifest when a user attempts to launch the Jitsi Actvity from a Widget... for example.

https://developer.android.com/about/versions/pie/android-9.0-changes-all#fant-required

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

This may happen due to API misuse, but also in complex applications where
activity lifetimes are not straightforward.

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

Ref:
https://developer.android.com/reference/android/app/Activity#setVolumeControlStream(int)

Looks like audio devices must be re-set after focus was lost and regained.
Otherwise some devices (tested on a Samsung Galaxy S9) are in a weird state
where the second microphone is not used when speakerphone is on.

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