Moves sendTones implementation to TraceablePeerConnection. It will be
responsible for creating/storing a DTMFSender. JitsiConference will
use the currently active TraceablePeerConnection to send the tones.

This fixes a bug where DTMF tones can not be sent after
JingleSessionPC/TraceablePeerConnection instance changes.
The JitsiDTMFManager instance was referencing invalid PeerConnection.

The client will reject P2P session-initiate if the conditions which
allow for P2P session to start are not met(there more or less than 2
human participants in the call).

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.

This functionality is being brought back for apps
that use ljm for its prosody logic but not for
video conferencing, ie Jitsi-Meet Spot. The desired
use is for Spot-TVs to be identifiable by their
jid alone and for the resource to be the part
that identifies them.

* Adds confID to JitsiConference option and enables callstats siteID.

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

* Detects whether a participant is jigasi and sets a property.

* Fix empty param.

* Removes nested function.

* Updates kicked event to inform local and remote kicks and who it affects

* Parses actor from MuteIQ and adds participant info to mute track event.

* Fixes emitting both events.

* Fixes comments.

* Add error description

* Change error message

* Change error message

Because it's possible to go back from ICE FAILED state to CONNECTED it's
better to give it some time until the XMPP connection recovers and only
if they ICE does not recover in time send the ICE failed notification
to Jicofo. It's done by sending a ping to the XMPP server and checking
the ICE after 2 seconds past the ping successful response.

Make the client send ICE failed notification to let Jicofo know
that the ICE connection with the bridge has failed. It can then
re-create the channels and send new transport in the
'transport-replace' message to give it another try.

Also adds a bridge session ID so that Jicofo can discard outdated
requests. When a bridge dies multiple clients may send ICE failed
notifications at the same time. Jicofo will detect bridge failure
when processing the first one and it must not act on the following
requests for the broken bridge session which is no longer current.

A bridge session ID will be sent in new 'bridge-session' XML element
which is part of either 'session-initiate' or 'transport-replace'
message. The server's region is moved to this element as well as
it's part of a bridge session.

* Fix: Old JitsiConference instance remains listening on incoming calls after leave - rejoin to same room

* Remove all listeners added by setupXMPPListeners

Updates speakers stats with values received by the spealerstats component, all the logic is activate only in case we discover speakerstats component address from disco-info and the incoming message is coming from that component.

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.

* feat: Read the server region from Jingle and broadcast it with statistics.

* feat: Adds the bridge count to local "statistics", refactors conference-properties.

* fix: Emits the conference properties with the event, small fixes.

* ref: Orders the imports alphabetically.

As described by @virtuacoplenny:
[T]he ordering is based on import path, not import name, with different
file depths being grouped together, node modules being grouped together
at the top.

* fix: Keeps JitsiConference#properties always defined.

* fix: Does not fire an event when the argument is undefined.

Emit ACTION_JINGLE_SI_TIMEOUT analytics event if it takes too long for
Jicofo to send session-initiate (it usually arrives within 1 second).

The options are coming from the config anyway.

* feat: Adds the user's region to presence. Fixes typos.

* feat: Measures end-to-end RTT with ping over the data channel.

* feat(conference): expose method to select multiple participants

* squash: fix typo

* squash: reduce to one code flow

* squash: default to empty array to mimic previous null default

* squash: fix typos, change docs, default params

* squash: remove defaults

* squash: update comment about array arg

* Uses json message extension

* Sends json-message without the body element

* Info comments and parameter order changes

* ref(recording): change implementation to match VideoSIPGW

VideoSIPGW takes in a chat room and uses instance variables
on the chat room. RecordingManager has been changed to
mirror this approach because of the case where jitsi is
deployed on a domain requiring authentication. In that
case, the initial chat room is created and fails, a
new chat room (connection) is created for authentication,
authentication is put onto the failed chat room, and the
failed chat room is used. As such, recordingManager
should not be tied to chat room creation itself but
rather tied to the first chat room.

* squash: use git mv to detect capitalization change

Adds a getter to retrieve JitsiConnection instance used by
the JitsiConference.

JitsiConference shouldn't lie that the leave() was successful when it
was not.

* 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

* feat: Exposes sending JSON payload through XMPP.

Incudes only the payload when firing events for JSON trannsported
through XMPP.

* squash: Addresses feedback.

* squash: Addresses more feedback.

* feat(recording): show the YouTube live stream URL

- Pass you_tube_broadcast_id to Jibri so it can create a
  YouTube link for the live stream.
- Emit the liveStreamViewURL (the YouTube link) when it
  is received from the participant doing the recording.

* set member.liveStreamViewURL only when truthy

Will emit CONNECTION_ESTABLISHED event to fill up the gap where the lib
users are not able to tell whether or not the connection has been
established if there were no interrupted/restored events emitted.

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