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.

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

Token is passed as parameter when creating JitsiConnection and we no longer use it from the options passed to the connection.

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.

Our JSHint configuration is not extensive and we have excluded multiple
files from linting. Additionally, we have seen JSHint to be unable to
parse newer ECMAScript features such as the object spread operator
(proposal).

On the other hand, we have seen ESLint to beautifully work on React and
React Native source code in addition to ES2015 and later. Introduce
ESLint alongside JSHint as an intermediate step to eventually switching
from JSHint to ESLint.

As our source code does not fully follow even the JSHint rules we have,
it is very difficult to introduce ESLint with many rules. At the
beginning, introduce it with as little rules as possible. Morever,
ESLint is able to automatically fix certain rule offenders so once we
have ESLint merged we can incrementally add new rules while keeping our
commits' modification on as little subjects as possible.

By default talk while muted detection is disabled.