This cleans up the method call, where some duplicate data was passed.

The 'options' identifier is used for different objects, which has lead to a bug where
the object that passes along the 'config.js' provided data is lost along the way. Code
that's further down the execution stack still expects to process that configuration,
which indicates that not passing it along is unintentional.

With this change, an Android device will adhere to the value defined in the 'resolution'
value of config.js, something it currently does not.

It's supported in Chrome >= 65.

* ignore duplicate jibri status updates

* re-add mistakenly removed return

Until M69 Chrome used to consistently emit "onstreamadded" when
audio/video stream is added for the first time and then emit track
events only if the stream is modified afterwards (video track replaced).

However it looks like now it can first emit "onstreamadded" and then
additional "ontrackadded" for the MediaStreamTrack that was already
included in the MediaStream signalled by the "onstremadded" event. I
have not managed to figure out what is causing this and the only
difference in the SDP is the fact that the remote peer (JVB) includes
IPv6 candidates. Anyway it doesn't hurt to have such a safeguard.

The 'self.errorCallback' was passed incorrectly - it should have been
bound to 'self' eventually, but now the arrow function is the preferred
way.

Safari 11 has `navigator.mediaDevices.ondevicechange` but doesn't define
`navigator.mediaDevices.addEventListener`. 🤦

Fixes: https://github.com/jitsi/lib-jitsi-meet/issues/823

Just skip it in such environments, such as React Native.

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.

We now use PeerConnection promise-based APIs, which were introduced in M51.

This function helps simplify the code when handling browsers that are pretty
much Chrome in disguise.

* feat: Read the server region from Jingle and broadcast it with statistics.

* feat: Adds the bridge count to local "statistics", refactors conference-properties.

* fix: Emits the conference properties with the event, small fixes.

* ref: Orders the imports alphabetically.

As described by @virtuacoplenny:
[T]he ordering is based on import path, not import name, with different
file depths being grouped together, node modules being grouped together
at the top.

* fix: Keeps JitsiConference#properties always defined.

* fix: Does not fire an event when the argument is undefined.

Chrome fires devicechange twice. This causes the DEVICE_LIST_CHANGED
event to fire twice. The listener in jitsi-meet has async logic
to handle the event, including creation of new tracks. So it
can happen that two devicechange events fire, the jitsi-meet
listener fires twice, creates duplicate tracks, and uses both
tracks. Diffing the device list for an actual change is a workaround
against extra devicechange events.

Note: this does not solve the issue in jitsi-meet of it not
handling quick successive DEVICE_LIST_CHANGED events.

Keeps it consistent with the previous implementation.

When using the Promises API, modern constraints are used, so adapt to it and use
the modern versions.

Just use navigator.mediaDevices.enumerateDevices().

It's 2018 after all...

Get rid of all wrappers and use navigator.mediaDevices.getUserMedia, since all
supported platforms have it by now.

Also use the unprefixed versions of WebRTC APIs.

The previous check looks like it was meant to check if it's
the initiator.

The options are coming from the config anyway.

* feat: Adds the user's region to presence. Fixes typos.

* feat: Measures end-to-end RTT with ping over the data channel.

* feat: Adds a couple of permanent analytics properties.

- Don't use it on supported browsers
- Make sure no stray timers are left

* Enables adapter for edge.

We were not filtering correctly all unsupported iceServers and an error is thrown and no connection is established.

* Enable desktop sharing for Edge.

Currently when replacing video track with desktop sharing one, doesn't work because of: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/17528460/
If Edge user joins first and enables desktop sharing it will work when others join. Tried also to use replaceTrack/setTrack as a workaround, but again we hit an error, this time InvalidAccessError.

* Adds the helper function usesAdapter in BrowserCaps.

* feat(conference): expose method to select multiple participants

* squash: fix typo

* squash: reduce to one code flow

* squash: default to empty array to mimic previous null default

* squash: fix typos, change docs, default params

* squash: remove defaults

* squash: update comment about array arg

* ref(video-quality): cache max frame height and send on channel open

Currently it is possible to try to change the max receive video
frame height before the data channel is open. In that case an error
will be thrown. This change makes it so that the desired frame height
is saved and sent on channel open, avoiding the thrown error the
max receive video frame height logic is exercised through the
JitsiConference api.

* squash: do the second part of the actual fix

* Change layer suspension to use parameters in RTPSender

We no longer suspend unused simulcast layers via a bandwidth cap in the
SDP, instead we'll use the new parameters in RTPSender to enable and
disable streams explicitly.  The main advantage here is the RTPSender
method ramps up immediately when we re-enable the layers (as opposed to
the SDP bandwidth cap which took 30+ seconds).

* Fix linter issues