Use the W3C Permissions API where possible. At the time of this writing this is
supported in Chrome >= 64.

The code for handling device availability has been disabled for a long time,
plus it's ill named since it represents 2 abstractions: lack of permissions and
lack of devices.

Time for it to rest in the git graveyard.

There is nothing asynchronous about the initialization process (anymore), thus
turn it into a synchronous method.

In addition, WebRTC support is absolute, it cannot change from not being
supported to being supported (as it plreviously could, thanks to Temasys) so get
rid of the ancillary logic to support that.

Last, introduce a way to check if WebRTC is supported in the current
environment: JitsiMeetJS.isWebRtcSupported().

Also, updatee the documentation section on connection errors.

* Uses optional statsId to report to callstats and push it to presence.

The feature is behind a flag which is disabled by default.

* Renames statsId to statsID.

* Fixes doc.

This is performed by stripping all traces of H.264 from the local SDP before
passing it to `setLocalDescription`.

Instead of failing with an error if another operation is in progress, which is
impossible to know as a user, chain them using the primises API.

* feat: add 'disableDesktopSharing' option

* ref(ScreenObtainer): simplify init

Some browsers may not support data channels (hi there, Edge!) and sometimes it
may not be desirable for other reasons.

* Get local user ID

How to get the id Participate local.

* Correction of the sequence of numbers

Ignores start audio/video muted requests received by jicofo.

Make sure there are options to set the extension ID and an enabled flag for
both Chrome and Firefox.

Removed checking for deprecated configuration options: desktopSharing,
chromeExtensionId and minChromeExtVersion.

By default talk while muted detection is disabled.

Jicofo is smart and can find any bridge with service discovery and/or
pubsub.