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

There is no need for setting the availability of desktop sharing anymore. It can
now be detected on the spot.

The reson for the previous code was that way back when browser extensions were
needed, it was possible to start a conference without desktopo sharing support
and get it afterwards. This is no longer the case.

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

This fixes an issue where lastN is not bumped to 1 on an audio-only client when a screenshare source is added to the call.

Take into account the start muted values stored in local storage.

Participants that join video muted do not have video tracks attached. Fixes https://github.com/jitsi/jitsi-meet/issues/7942.

Through several avatar work iterations it's no longer used.

I don't know how to modify built-in MediaStreamTrack type, so ignore the error.

...so that the text is more readable in the presenter mode. Chrome by
default uses 'detail' for screen sharing. I went with the 'text' here,
because the docs[1] say "may take advantage of encoder tools that
optimize for text rendering." - whether that's good specifically for
the presenter mode I don't know. It looked good for me when tested
on Chrome.

https://www.w3.org/TR/mst-content-hint/

Use fetch(), which gives us better control over headers.

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

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.

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.

This fixes the issue where the local preview appears muted when presenter camera is turned on and then off while screenshare is in progress.

Decode URLs using punycode when rendering, so when http://ebаy.com is sent
we render http://xn--eby-7cd.com/ instead.

Ref: https://github.com/tasti/react-linkify/issues/84

- Don't initialize handler's is their API key is not set
- Don't swallow exceptions when creating handlers
- Don't remove all handlers if an external one fails
- Dispose the analytics subsystem if no handlers are registered