RIP xenial

Keep one locale file for Russian language

chore: Removed "dev" from 2.3 versioning in settings.yml

chore(guest): pt/es guest lobby localization

feat(bbb-html5): localize guest-wait.html (part2)

Makes Libreoffice Docker mounts the system fonts

feature(bbb-html5): localize guest-wait.html

chore(locales): Pulled HTML5 locales; Added Afrikaans

Fix layout broken when close waiting room panel

fix(chat): reduce re-renders in chat recompute heights

Recording: Fix handling of recordings without recording marks

feat: Add button to close mute alert

refactor: remove unused class from component

Improve feedback to user after a failed file upload

Add configuration for max length typed answer in poll

refactor: remove unused code

This introduces initial translations for the guest-wait pages.
The only supported languages are en and de for now. Needs a concept
to hook it up with transifex.

Previously, bbb-record --rebuild was restarting recording processing
from scratch by creating the .../recording/<meeting_id>.done file. This
causes the recording to be reprocessed starting at the archive step.
However, re-running the archive step for an existing meeting is not
really supported! Ever since the segmented recording code was added, it
shouldn't /corrupt/ the recording files, but it's still not good.

And as a side-effect, re-running the archive step will re-create the
.norecord file for meetings without recording marks, meaning that you
cannot use bbb-record --rebuild to force a recording without marks to be
processed.

Switch bbb-record to restart recording processing at the sanity stage to
match the BBB 2.2 behaviour. Rather than have it insert tasks directly
into resque via redis-cli, it goes through a ruby wrapper that performs
input validation and uses the resque apis.

 - lump other responses in the poll and include in the display

Cutoff poll responses

 - limit display of responses to 7 to prevent squishing of display in the whiteboard

In the case where a meeting had recording enabled (record=true on create
call) but the presenter did not start recording during the meeting,
recording processing needs to be stopped after the meeting data is
archived, but before the recording formats are processed.

In the current 2.3 code, processing is halted after the "sanity" step.
However, the 2.2 code stopped processing after the "archive" step
instead. The main difference is that the scripts in the "post_archive"
directory (which are actually post_sanity scripts) did not get run on
non-recorded meetings for 2.2. This behaviour should be preserved for
compatibility.

I have added a special exception to trigger halting processing for a
recording job without causing the entire resque job to be marked as
failed. It only causes the `schedule_next_step` method to be skipped, so
following jobs won't get automatically run. This fixes #11877

Make random user picking coundown (UI + audio) optional