For browsers that don't support headerBytesSent in RTCOutboundRtpStreamStats
neither headerBytesReceived in RTCInboundRtpStreamStats, we are now able
to calculate upload and download rates.
We are also able to get transportStats information for browsers that
don't support iceTransport attribute of RTCDtlsTransport.

We now show jitter, lost packets and turn server informations

Added support for getStats in screenshare's service. This works similar
to the getStats for video provider, and the information retrieved from
screenshare is added to the video information for cameras.

When audio is inactive, the browser shows an error related
to this undefined reference.

This information is also retrieved when copying data to clipboard

We also adds this information when copying data to clipboard

The specification has more details about each field returned in stats
dictionaries.

We now retrieve update information about active video peers, and calculates
download and upload rates. These rates are the sum of data transfered in
all video peers.
Screenshare stats is not being added to the sum, yet.

Using getStats api and peer information to retrieve upload/download rates
and transport information

Adds a label in connection status modal,
where users will be able to copy information to
clipboard.

Until now we only logged for `normal`, `danger` and `critical` leading to some ambiguity in log analysis

Should fix an issue with the recent Chrome 92 intervention that limits
the number of concurrent WebMediaPlayers (an inner element of
HTMLMediaElements) to 75/40.

Webcam video elements were being left dangling in paused state despite
the elements themselves being cleaned up from the component. That
generated a skewed accounting of WebMediaPlayers in the session.

After reconnecting (with 1007 or 1005), user may gets 1005 when meeting
is ended by moderator.

We now let audio-manager log errors, using the specified error code.
These errors are still logged in bridge layer, but as a warning.
This commit doens't change error codes behavior, they are still being
logged as errors and with the same code numbers.

Initialize the start/stop dictation button when speech recognition stops after some silence (#12783)

* Update component.jsx
* Update en.json

the speech recognition can stop due to the incompatibility of browser as well.