* feat: Adds option to set ws keepalive url through config.

* chore(deps) lib-jitsi-meet@latest

* feat: Adds option to set ws keepalive url through config.
* fix VADAudioAnalyser: catch error

be18ff34be/...9fdde46694d1c4bc8b7f051cc8d50e0df29ffd07

RN doesn't support RTCRtpSender yet. Therefore, media is suspended on RN by changing the media direction in the SDP whenever the client receives an ideal height of 0 for sender constraints on the bridge channel.
LJM update - 3570339360/...be18ff34bedf38c7475fe4953074c7959000e15f.

831716c160/...3570339360763fa0911d92c5ae7c270860b6934b.

Support processing stats in the spec-compliant format.

* feat: Uses mod_external_services supporting urn:xmpp:extdisco:2.

The old mod_turncredentials.lua is left to continue working for those using old installs.
New install will start using the new module which will no longer be needed with prosody 0.12.

https://hg.prosody.im/prosody-modules/file/4841cf3fded5/mod_external_services/mod_external_services.lua

* squash: Updates ljm to support urn:xmpp:extdisco:2.

https://github.com/jitsi/lib-jitsi-meet/compare/...94ac35ae818093896e639e74f5fc389b488206a0

* feat: Detects shard changed when using websockets. (#1462)

1009693f2e/...cb484cf48ccd3d56cf9bb2e9d452bd7aa644ac8a

    When an endpoint that doesn't support the preferred codec (VP9) joins a conference, all the other endpoints fallback to VP8 until the endpoint leaves the call.

Stats timestamps were incorrectly formatted, fixed upstream.

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

* fix: Disabling lobby when using tenant.

87c6e37475/...7896fc8b92f1416f800b56c87e51fb69700d620d

Will now work even if installreferrer or GCM are missing.

* feat: Skip p2p when the participant is jigasi.

1fd7256553/...87c6e374755718fdb0804c2c798ea4bc832f4fca

Fixes icons not rendering on iOS 11.

*  feat: Skips using disco-info for features. (#1450)
* sdp: improve sdp matching for simulcast lines (#1452)
* sdp: add missing colon to findLines calls (#1447)

310983c5b0/...1fd725655357db161d40e7dd52ef111e2b04bd68

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

* fix: Skip sending multiple times disco-info to jicofo.
* build(deps): bump ini from 1.3.5 to 1.3.7

9f65e8fab3/...8bb653f1d6d450f4d17f56eb6bd4c353138f6829

Bumps [react-native-webview](https://github.com/react-native-community/react-native-webview) from 10.9.0 to 11.0.0.
- [Release notes](https://github.com/react-native-community/react-native-webview/releases)
- [Changelog](https://github.com/react-native-webview/react-native-webview/blob/master/.releaserc)
- [Commits](https://github.com/react-native-community/react-native-webview/compare/v10.9.0...v11.0.0)

Signed-off-by: dependabot[bot] <support@github.com>

chore(deps) lib-jitsi-meet@latest

Helps with testing turn relay cases.

chore(deps) lib-jitsi-meet@latest

Also, default to libravatar.

Closes: https://github.com/jitsi/jitsi-meet/issues/4927

chore(deps) lib-jitsi-meet@latest

Safari 14.1 has a bug where it returns 720p for every simulcast stream when RTCRtpSender.getParameters is called even though the stream resolutions are different.
By using the encodings config used when source was added, on every RTCRtpSender.setParameters call, we ensure that simulcast stream resolutions don't change.
chore(deps) lib-jitsi-meet@latest

Do not resize the desktop share to 720p by default when the desktop track resolution is higher than 720p. This is causing bluriness when presenter is turned on.
Remove the 'detail' contentHint setting for the desktop+presenter canvas stream as it forcing chrome to send only 5 fps stream for high resolution desktop tracks.
Move the desktop resizing logic behind a config.js option - videoQuality.resizeDesktopForPresenter.

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

chore(deps) lib-jitsi-meet@latest

lib-jitsi-meet@latest

The previous one no llonger works out of the box with RN.

The URL polyfill we were using didn't support taking a URL object in the
constructor, the updated one does.

This update doesn't touch thousands of lines of package-lock which caused a
runtime breakage on both platforms.

This reverts commit cd68c72338.

Fixed by patching react-native:
e7ee500660

(backport from upstream)