Also unify the mobile and web features into one, even though internally they still have separate ways to enable the functionality.

* Added new config to enable individual sharing features

* make config values url friendly

* Add new setting to whitelist

* Fixed some linter issues

* Fixed more linter issues

* Fixed merge error

* Check if interfaceConfig is defined

* Only show more numbers link if there is more than one number

* fix(RTCUtils): Init availableDevices.

e6ef4e7ae9/...f1ec96678002a88a0a87bb0a6fec1f5d642813d2

* fix(RTC) fix device selection not being available
* fix(TPCUtils): undefined is not an object (evaluating 'this.tpcUtils.replaceTrack(e,t).then')

4c668023b3/...e6ef4e7ae974e054d6647d05718c18f678ed3e9c

* fix(TPC): Remove the existing track instead of overwriting. When a second remote track of the same mediatype is received for an endpoint, remove the existing track before creating the new remote track.

9beb47fe5f/...4c668023b38c92615cd06c4e90006246c3e4aa2c

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

We use TFLite now so this is unused.

That means all browsers except Safari, for now.

In addition, use the 96p model (instead of the 144p one) on browsers without SIMD support.

* Added mute video feature

* Fixed export

* Fixed some issues

* Added remote video mute notification

* Fixed import

* Fixed conference event handling

* Fixed some linting issues

* Fixed more linter errors

* turn screenshare off on remote video mute

* Fix linter issue

* translations added for mute video feature

* Added video mute button to interface config

* Updated lib-jitsi-meet

* Fix copy paste error

Co-authored-by: nurjinn jafar <nurjin.jafar@nordeck.net>

* fix(e2ee) fix disabling E2EE
* fix(e2ee) fix key index after ratchetting
* fix: Drop caps handling (#1495)
* fix(SendVideoController): Apply the sender constraint only when it changes. There were cases where the bridge was sending the same constraint multiple times causing redundant calls to getParameters/setParameters on the RTCRtpSender.
* feat: Use the new bridge signaling format.
* fix(gum) update permissions prompt detection

c534f74884/...6a7b16c33e27481b03e5a37636e72426c0848265

Co-authored-by: Gabriel Imre <gabriel.lucaci@8x8.com>

fix(gum) add event handling for SLOW_GET_USER_MEDIA

Show an overlay with a spinner when slow gUM is fired

* Add buttons to send messages/set nickname.
* Redesign message/nickname inputs.
* Pin messages to the input.
* Add keyboard avoider for Safari.
* Make chat content scrollable on mobile.

* fix(SendVideoController): Apply the sender constraint only when it changes. There were cases where the bridge was sending the same constraint multiple times causing redundant calls to getParameters/setParameters on the RTCRtpSender.
* fix(gum) update permissions prompt detection

beaff3dd02/...7f919faaccb268ef307d619992260919a6535e95

* feat: Use the new bridge signaling format.

c534f74884/...beaff3dd02e9e99da2f61c2a9ed5ca3a34d51dcf

* feat(load-test): Senders unmute themselves if muted by policy.

* feat(load-test): Adds option to skip creating local audio track.

We currently create local audio track even when starting audio muted. Adding the option to control that can load test that for clients or signalling.

When there's no jitsiTrack set on the base/tracks entry it means
a track is being created (get user media is in progress).

Use the Google Meet model and SIMD optimized WASM.

* ref(QualityController): Split send and receive video constraints handling.
* fix: Save guards _features to be always empty and nver undefined. (#1493)

d1f0ab4d5a/...c534f748849a308d08b06e306f5a66709ccae056

* fix(load-test): Always create local audio track.

When audio mutes will mute the track. Also fixes previous change where we do not add any of the tracks to the room.

* squash: Fix lint errors.

Behaves now as the main client, and skips few unnecessary presences.

* fix(GUM-permissions): cache permissions on init.
* feat: Reuse billingId from localstorage as jitsiMeetId.
* fix(example) simplify
* feat(docs) mvoe API documentatrion to the handbook

84357ce1a8/...d1f0ab4d5a691f438f7d4c7446f29273b1b8fcdc

Introduces a new feature flag ('help.enabled') and uses that to
determine the visibility of the 'Help' button in a call.

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

This basically reverts
a3fb996ff0
while retaining the same properties that prompted it's original intent, namely
avoiding sending the Referrer header.

When the method was called from Swift they were collected before calling them.