While the base URL remains configurable, this patch reverts back to using
Gravatar.

We noticed high latency with libravatar and contacted them. They are in the
process of migrarting to a better infrastructure (it's a single personal server
at the moment) so we'll re-evaluate once that has happened.

As for why not leave the default and change it on the meet.jit.si installation,
we don't want to kill their server :-)

If limitLastN values are specified and channelLastN < limitLastN, configure channelLastN on the conference.

Also, default to libravatar.

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

We stopped providing a way to set them, so don't render them either.

Also cleanup some leftover config options.

* feat: Drops filmStripOnly mode.

* squash: Let's make lint happy again.

* squash: Drop some css.

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

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

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.

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.

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

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

This change serves 2 purposes:

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

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

* fix(config) remove unused options

* Update configWhitelist.js

* Display of the logo has been reworked (simplified).
* The logo will not be displayed if the call to `branding` endpoint fails.
* Add more docs.