Error handling was added to ensure some munging helpers
were receiving RTCSessionDescriptions. Temasys is doing
something else and is passing its own object into
the mungers. So, let temasys do that.

IE11 errors when adding a temasys media stream object to
a Set. So instead use an Array.

AnalyticsAdapter is initialized on file load. The constructor
calls a method that calls Object.assign. All this happens
before jitsi-meet has loaded polyfills. So, instead
initialize permanentProperties inline with the expected
values, avoiding Object.assign.

Safari will fail to set its remote description if no
supported video codecs are found. This can happen with
config.p2p.disableH264 set to true, as browsers will strip
H264 from their offers. To get around this problem in a way
that can be removed once this is fixed on Safari's side,
add a function to inject H265 before setting the remote
description.

* revert: Reverts be665cbff7.

* ref: Renames "peerjid".

* ref: Refactors the initialization of a peer connection.

* feat: Re-implements the A/B test for the "suspend video" feature.

* squash: Deep copy.

* ref: Renames forceSuspendVideo to abtestSuspendVideo.

Ssrcs not grouped together in the jingle element
are not recognized by the bridge. When parsing an
sdp with ssrcs that are not listed consecutively
it is important to still group them together
in the jingle element.

* ref(sdp): lower logs about missing local video to warning

* ref(sdp): earlier error handling for missing description and mlines

* ref(sdp): rename maybeMungeLocalSdp to be more specific

Firefox has deprecated modifying a description's sdp through
re-assignment. Safari (without temasys) does not allow it.
As such, wherever the sdp has to be modified instead create
a new description with the modified sdp.

Upgrade flow to 0.53.0

Required for jitsi-meet upgrade

* feat(adapter): use with firefox

* squash: add comment about sdptransform workaround

- Add a new browser check so adapter shim usage can be gated.
- Get track resolution for stats from the track itself to account
  for browser resolution fallback logic. Do this only if
  we can be sure adapter has shimmed it in.
- Create a new getUserMediaFlow, with RTC being the orchestration
  for various RTCUtils calls.
- Remove connection quality stat "resolution" which was being
  emitted but not used but listeners.

remove invalid test and run tests pre-commit

* use the centralized jitsi eslint config

* remove redundant extends

* Loads CallStats backend only after the script has finished downloading.

* Updates jsdoc and log level.

* Updates jsdoc.

Do not log whole objects on Jingle error, as these may cause trouble on
iOS react-native.

Update strophe and use it via imports.

With p2p, inactive lines in the sdp should not be
ignored. Inactive is used to suspend video transfer
to the bridge when dropping back to p2p mode.

To install the chrome webstore extension, the user must already have installed "Download Chrome Extension". On missing extension we open a popup window which allows the user to add the extension and then install it.

chore(deps): remove unused.

Sends applicationVersion to callstats.

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

feat(RTC): fix using 720p resolution by default

The default was still 360p if the option was missing from config.js. In
addition, move the logic outside of a browser check, so all browsers get
glorious HD by default.

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.

feat(remote_mute): Add analytics event

detectChrome() detects the browser but then may throw an exception while
parsing its version. The exception could be reproduced by toggling the
device toolbar and instructing Chrome to identify as iPhone 6 Plus.