I see we have an option to use replace track in conference level which its missing in this API. thanks

* feat: Skips pinging when there was a recent server response.

* feat: Adds options to control xmpp ping settings.

* fix: Fixes wrong default value.

* squash: Received messages in ping interval sets failed ping to 0

Signs and verifies frames. For now this is done on every frame.
This is not the long-term goal and there needs to be a better strategy.

* added setLocalParticipantProperty doc
* PARTICIPANT_PROPERTY_CHANGED event doc added

* fix(docs): refactor and fix formatting
* fix(docs): add missing options
* fix(docs): change confusing link naming in README

Closes #1272

Always attempt to discover the configured STUN/TURN servers.

this uses the full four bits in the wire format. The wire format
looses the (currently not implemented) extensibility with variable
length keys.

similar to what is explained here:
  https://tools.ietf.org/html/draft-omara-sframe-00#section-4.3.5.1
but we do it on authentication tag failures since it is not possible
to tell whether decrypt.

following
  https://tools.ietf.org/html/draft-omara-sframe-00
but putting the frame metadata into a trailer instead of a header.
We call this JFrame.

Also the key we get from OLM is high entropy so we do not need
to use PBKDF2 but can use HKDF instead. See
  https://wiki.developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/deriveKey#HKDF

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