* fix(Toolbox) Maintain overflow button visible at all times

* Make changes only on desktop browser

* feat: Drops filmStripOnly mode.

* squash: Let's make lint happy again.

* squash: Drop some css.

This will make browsers not cache results in cleartext.

Co-authored-by: Tim Dittler <t.dittler@heinlein-support.de>

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

It has been `true` for a very long time.

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.

The main config contains disableRemoteMute and remoteVideoMenu: { disableKick: true} options, which can be used.

Introduced a config property to disable profile.

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.