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.

If a failure occurs while we are still setting up the UI it's possible the local
thumbnail is still null, and none of the code assumes it may be null, so skip
it.

We are off my 1KB oh well.

Fixed by patching react-native:
e7ee500660

(backport from upstream)

Fixes an issue when the video quality dialog is opened for first time
and config.videoQuality.persist is true there isn't any selected option.

Watch out when updating beyond this version:
https://github.com/react-native-community/react-native-svg/issues/1354

This change serves 2 purposes:

- (Hopefully) make the recent list entry options easier to discover
- Remove the (now unmaintained) swipeout dependency

Change the preferredVideoQuality and maxReceiverVideoQuality values to Ultra HD resolutions. The requested resolution can be as high as 4K to facilitate VPaaS customers to request 4K. The sender video resolution will always max out at the value specified in the video constraints from config.js settings.

Always attempt to discover the configured STUN/TURN servers.

Disable RTX on FF

If the WASM code could not be loaded, fail to initialize if and remove it from
globals so the E2EE option becomes unavailable, since it will be non-functional.

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