Setting the waiting state false as default was leaving an open gap where
the users still did not have a valid breakout room's join url and it's
join button enabled.

Change the first waiting state to true and handle the join type as the
component finishes mounting. If it's a free to choose room scenario,
dispatch the whole Promise based solution and let it manage the waiting
state as the interval checks for the URL response.

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.