- Use getDisplayMedia on browsers where it is supported.
- desktopSharingChromeDisabled and desktopSharingFirefoxDisabled will no longer be supported.

derived from the participant id in addition to the salt, separated by a null
byte to avoid ambiguity attacks along the lines of
  (someRoom, someParticipant)
  (someRoo, mSomeParticipant)

* feat(video-quality): control the sender resolution based on video quality settings

* fix(video-quality): Apply the settings on newly created p2p/jvb jingle sessions
If a p2p/jvb session is not present when setSenderVideoConstraint is called,
make sure the settings are applied when they are created

Moveѕ e2ee operations to a worker that is included as text/blob for now
to simplify deployment.

fixing some minor issues and updating the description of the behaviour
when there are decoding errors

adds a document describing the high-level design of the current e2ee approach

The LipSyncHack is currently broken in Jicofo and
will lead to unstable behavior.

It can either be a websocket or bosh URL, so the current naming is
confusing.

* feat: implement vad noise detection

* start detection services on initial track add

* additional refactor / calibrate noise detection

* stop detection services on track remove

* address code review

* address code review p2

To be sure we always report room name in small case and as mobile and jigasi report this way it will take time for them to adopt which leads to wrong stats.

* Adds confID to JitsiConference option and enables callstats siteID.

* Simplifies siteID logic and use '/' as default when there is no tenant.

1. JitsiMeetJS.createLocalTracks constraints missing data.
2. removed duplicate documentation for selectParticipant.
3. added setReceiverVideoConstraint function data.

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.

1. The example was using the Promise return value of JitsiMeetJS.init
which is no longer possible/correct after commit "core: refactor
initialization not to return a Promise".

2. We went back and forth with the value returned by JitsiMeetJS.init:
we initially didn't return a value, then we started returning a Promise,
and now we're not returning a value. Whether we'll go back to returning
a value is up in the air. Anyway, the return value is practically
determined by the last in a chain of function calls: JitsiMeetJS, RTC,
RTCUtil. Since the chain is not really documented, it will not hurt much
to make it easier to refactor the chain by "composing" the functions.

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().

localTracks[i].stop();
As localTracks doesn't have stop function , coz of this line getting error and user was not able to left the room or unload 

So changed it to :
localTracks[i].dispose();

* feat(recording): frontend logic can support live streaming and recording

Instead of either live streaming or recording, now both can live together.
The changes to facilitate such include the following:
- Remove the old recording.js module which allowed one recording at a time.
- Remove events for live stream url changes as the url is now part of a
  sesssion and not fired independently.
- Availability of sipgw and recording are gone. Instead sessions have a
  failure reason. For sipgw sessions, store that failure and emit it to
  listeners.
- Create a new recordingManager singleton that can start/stop sessions
  and handle updating known state of those sessions. Known state is
  emitted through one event.
- Create a JibriSession model to encapsulate state of a session.

* update comments, use map to store sessions

* always pass in focusmucjid

* try to fix jibrisession docs and remove default null

After running `npm install` I end up with a minified library for lib-jitsi-meet. I had to adjust the name to get the example to run

In order to include browser capabilities in RTCBrowserType I needed to
refactor RTCBrowserType.

Added descriptions for user identifying information in JWT tokens
Added better descriptions of prosody configuration settings when accepting JWT tokens

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`.

ESLint 4.8.0 discovers a lot of error related to formatting. While I
tried to fix as many of them as possible, a portion of them actually go
against our coding style. In such a case, I've disabled the indent rule
which effectively leaves it as it was before ESLint 4.8.0.