fix(statistics): sendEventToAll was not passing string to callstats

Jingle and SSRC updates

ICE connectivity issues can be transient and those should not prevent
from sending SSRC updates. XMPP stream is a separate connection/stream
and skipping the updates while ICE is disconnected results in broken
media session where the stream information is not propagated correctly
across the conference participants.

Introduce JingleSessionState constants. Make the invalid JingleSession
rejection an explicit action taken by the JitsiConference.

Remove 'ssltcp' candidates when 'webrtcIceTcpDisable' = true

Fixes callstats feedback

Page reload overlay

Disable Temasys on React Native

Lib-jitsi-meet uses Temasys on Internet Explorer and Safari so it does
not make sense to require its adapter.screenshare.js on React Native,
for example, where it fails anyway.

Defaults to jitsi instead of focus for remote user id reported to cs.

Add 'failICE' config option

Fix temasys plugin support

The corresponding extension's name was changed
in Jicofo to 'bridgeNotAvailable'.

Fix JitsiConference.leave to return a promise.

The promise is resolved once we got confirmation of leave or a timeout expires in case of a problem.

Skips setting local track resolution in case of FF.

Updates to always use jitsi-meet-logger and print only errors for monitoring callstats callback.

Remove .babelrc to simplify React Native support

When the Temasys plugin is used the 'muted' property is in the track,
but it's value is undefined.

React Native's module bundler (aka packager) has its default Babel
preset - react-native/babel-preset - which it uses in the absence of a
custom .babelrc. Unfortunately, the default may be tripped by the
presence of a .babelrc in dependencies. Additionally, if the default
does not get tripped, the npm install of lib-jitsi-meet as a dependency
may fall into a recursion in which Babel attempts to transpile
react-native/babel-preset. To reduce the risks of stumbling upon such
problems, move Babel's configuration inside the Webpack configuration
file.

The flag when set to 'true' will enforce ICE failure. It is supposed to
be used in automatic testing.

Fix "no data from source" before ICE has connected

I added reporting of Promise's reject reason in b10a1fc while merging
jitsi/ss_postinstall_fix since Promise's reject function has such an
argument. Hristo Terezov disagreed with it because reason is undefined
in the use case and found it to be confusing so I'm reverting to what he
intended in the first place.

We can not assume that the audio source is not sending any data based
on the stat until the media connection has not been established.

fix(SS): implement interval to check the status of the ext after install

Simplify the source code by using some ES6 features such as arrow
functions to avoid the use of 'var self = this', the shorthand for
method definitions in object initializers.

Fixes sip calling.

In case of roomPass is undefined, an error occurs: Cannot read property 'length' of undefined.

feat(feedback): Tries to send the detailed feedback to analytics

ESLint

Switch from Browserify to Webpack

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.