bbb is used

moved avatar webcam to separate component.

(WIP) added virtual webcam for displaying an avatar. It can be activated from the video preview modal. TODO: use actual avatar from user - now the default avatar is used. it should be included as a fallback, though.

added switch for translation feature. it can be turned on/off by setting media.translation.enabled to true/false

merged 2.3.14 to feature/translation_2.2.31

Merge commit '669c8abe' into feature/translation-2.3.x

interpretation volume header is only shown when a slider is visible

https://git.fairkom.net/chat/fairblue/-/issues/97#note_35019

new channels by default

if no value found

replaced "Übersetzer" with "Dolmetscher"

chore: Pulled HTML5 locales for 2.3 on Sept 22, 2021

chore: Update axios and other npm deps

Fix: endWhenNoModerator not ending the meeting after all moderators left

Fix link to BBB tutorials on 2.3

Closes #13136
Same as #13137 but on 2.3 branch

fix: Add RTL support for network stats #13085

feat: allow users to see network stats and copy network data to clipboard

chore: Update missed trim-newlines reference

chore: Pulled HTML5 2.3 locales on Aug 26, 2021

fix(polling): stop current running poll

chore: update "ws" and "path-parse" versions

Recording screenshare audio fixes

Fix https://github.com/bigbluebutton/bbb-install/issues/413 in source

Disabling audio or video processing isn't really something that's part
of the working format (and at some point we might want to combine
audio+video processing together).

Move the setting of the '-an' and '-vn' options to where they're
required - as a detail of the EDL processing for video-only and
audio-only components of the output.

Honestly, the main reason for this change is that when testing alternate
working formats, I had accidentally dropped the '-vn' option from the
FFMPEG_WF_ARGS variable without noticing.

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.

As far as I could understand, polls are tightly coupled with the meeting
main content area, or at least they were and we still have to deal with
this close relation between them. Not sure if it's something we'll keep
this way forever but, from my candid perspective, looks like this is already
diverging inside the poll model. Polls are indexed by presentation pages,
screenshare or even something called "public" that I'm not 100% what
actually means. My best guess is anything besides the first and the second.

The polling stop process lacks to inform which pollId is scoped at source
so it relies on akka-apps to discover based on the current state of other
apps. This looks like the major problem over this polling termination issue.

Made a few changes at the running poll getter fallback at the polling stop
process. Following the premise that there is only one running poll available,
we make sure to return a valid running poll (if there's one).

We now show jitter, lost packets and turn server informations