upgrade node-sass version

fix: handle case of freeJoin breakout with no users

fix: Re-subscribe user to guestUser collection on promotion/demotion

fix: Grant current-poll access to attendee presenter too

fix: Check for users before grabbing breakout url

fix: webcam resize - RTL languages

fix(audio): improvements in audio logging

Stop dictation when swapping languages with the voice recognition on

fix(guests): Propagate list of pending guests only to mods

fix(polls): Avoid viewer manually subscribing to current-poll

fix(breakouts): Do not allow users to obtain 'redirectToHtml5JoinURL' for others

fix: Add meetingId to chatIds selector

fix(common-web): Sub-processes hang if output buffers fill up

ExternalProcessExecutor spawned sub-processes with stderr and
stdout buffers, but did not read from those buffers. Sub-processes
producing output sometimes would fill up these buffers and then hang
until the timeout occurs and the process is killed.

This fixes #12839 (PDF conversion hangs for 10 seconds per page)
by properly discarding command output. The patch also deprecates an
outdated and dangerous API and offers a safer alternative. Splitting
command arguments based on whitespace may result in unwanted behavior
if an argument (e.g. a filename) contains whitespace.

this.recognition can be null

fix: ConnectionStatus - log info on 'warning'

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

fix: avoid leaving dangling HTMLMediaElements in paused state (#12806)

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.