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.

When mic is locked, user is not able to talk so it doesn't make sense
to alert the user about unmuting (mute button is also disabled when mic
is locked).

Closes #12048

Complements #12705

Here's what we do when user activates mic:
1 - When we do something similar to listenonly's joining process
until we find a valid candidate-pair. The information about this
local candidate is store.
2 - We then start a new userAgent, and as soon as browser finds
a candidate with the same local ip address, we leave only this
candidate in the SDP and send this to FreeSWITCH. SDP should
contain only a single candidate.
3 - The rest of signaling process is basically the same.

More than 5 answers are now of Custom type poll and answers passed directly.
Increase A-I slide options detection