See: https://github.com/jitsi/jitsi-meet/issues/4720

This adds an option to disable video autoplay that will be used mostly with maleus (our selenium-based load testing tool for testing the new bridge). Disabling video rendering lowers the resource utilisation of the selenium nodes.

It's available on both Xcode 10 and 11.

* Adds notifications for who stop/start recording/live streaming.

* Updates to latest lib-jitsi-meet.

defined in RFC7050 instead of 'nat64.jitsi.net' as suggested by
Jonathan Lennox.

Fixes iOS crashes when restarting the AudioUnit in case of interruption.

It crashes like hell. See:
https://bugs.chromium.org/p/webrtc/issues/detail?id=11002

Adds option to limit number of outgoing calls per user.

Avoid Android crashes.

Uses sendBeacon to send xmpp presence unavailable on unloading the window(leaving the conference).

It was referencing LJM from a PR branch instead of the master.

If the Activity is put into the background before the ReactContext is created we
get an NPE here. While the window might be short, it's thechnically possible to
hit this, as our Crashlytics reports show.

The subsystem is set to the bundle ID and the category to "JitsiMeetSDK".

The call-integration middleware relies on it returning it, as iOS does.

Bring back the workaround introduced in afd2aea7
but removed in 21dcc41d. On conference join,
several other actions have already been fired
that try to set the large video participant
and select the participant on the bridge.
The problem is there is no conference during
these actions so the select participant
never fires. Then subsequent actions do not
fire select participant because the large
video participant has not changed.

This commit changes how the SmallVideo.isVideoPlayable method works.

1st we remove the check on the video stream muted field (materialized with the
!this.videoStream.isMuted() guard). This check is redundant as it is
already materialized in the !this.isVideoMuted check (the isVideoMuted
field is updated with the return value of the videoStream.isMuted()
method).

2nd we return false if we're in audio only mode, because it's
(obviously) undesirable to have a playable video when in audio only
mode.

react-emoji-renderer 1.0.0 removed the
thumbsup and thumbsdown aliases.

We try to load the configuration with every room change, even when there is no
room. There is a bad (corner) case: when we have no config cached (first boot or
wiped app data). In such case the user is trapped in an infinite loop because we
require the config to show the welcome page, oh well.

Pretend we have a configuration by creating the most minimal one to at least get
to the welcome page.

Simplifies the code a bit, and we use no lifecycle methods.

Audio streams are automatically played by WebRTC and this won't change, probably
ever. There is no point in having checks and an Audio component which does
nothing.