Clean up HTMLAudioElement used for notification sounds

After ending the notification playback, we set the ".src" property to null, which immediately stop the internal player of mobile browser (tested on Chrome for Android -  device list is on #11458).
For the specific list of devices, this prevents the internal buffer error "-61" described in #11458.
Fixes #11458.

Enable video-pagination and cameraQualityThresholds by default

Option to eject voice users with no matching user (re-submit #10959)

The lack of handling to check whether the user was a dial-in user when answering akka-apps periodic member probes was making it use an arbitrary default (callerName) as the userId, explicitly violating the convention that dial-in/outs should have v_memberId userIds

That would botch whichever added janitorial tasks that operated upon akka-apps GetUsersStatusToVoiceConfSysMsg probes

To be used with the ejectRogueVoiceUsers config option

Reconnects may introduce ghost voice users in a meeting when the client fails to
rejoin but the audio connection remains active.

While fetching for the voice conference user's status, apps can now check if a
voice user has a matching user record. If it doesn't, eject the voice user.

Preserve mutestatus when disconnecting/reconnecting microphone

After audio reconnection, a muted user would have it's microphone unmuted by default, unless muteOnStart is set to true. This fix this problem.
Fixes #9016

Make sure checksum validation is done first in join API and display an error without redirection in failure case

Don't validate insecure http urls for external video to prevent browser errors

Make sure checksum validation is done first in join API and display an error without redirection in failure case.

Cover clear screen share collection case

Clear meeting-time-remaining collection

Clear missing collections on meeting end

also adjusted moderator mobile video-pagination as suggested by @prlanzarin

One of the main issues in 2.2.x problem reports currently in the wild in social media and in the bbb admin groups seems to be that people turn a couple of webcams on and the clients or the server already can't handle it any more. In most cases, enabling video-pagination for mobile devices and also cameraQualityThresholds already "solves" the problem and makes it possible for much more students to attend online-class as well as raise acceptance of using BBB instead of other commercial services.
Even after promoting these new settings for weeks, many BBB operators still don't know of them and are surprised and happy once they enable it.
This change contians rather high values so that admins see that these features exist, but typical use cases which might not want video-pagination enabled (typical 28people school class) are still not "annoyed".

Set default cursorInterval to 150ms (was 40ms)

9101 add poll abstention

video-provider: fix inconsistent client state when a webcam being shared times out

Update axios to 0.21.1

Add heapdump threshold in settings

Prevent open textarea blocking dropdown menus

audio: fix talking-indicator mute debounce

video-provider: Revert "Improve 16x9 Support"

video-provider: make video-list-item actions dropdown keys unique

audio: add a configurable throttle to action-bar`s mute toggle

Fix wrong path in settings for audio constraints