On mobile web we want to keep both toolbox and hang up menu visible because they depend on each other.

Accessibility: keyboard navigation on the toolbar (Context menu)

* feat(visitors): Transcriptions for visitors.

* squash: Fixes filter iq.

* feat: Rewrites room name requests in rayo iq for visitors.

* squash: Handles visitors count that request transcriptions and the languages requested.

* fix(subtitles): Make sure we show captions button when no features but is transcribing.

* feat(toolbox/web): updated imports extensions and fixed some jsdocs

Currently if a button in the main toolbar is not visible, the button is
not replaced by another button from the overflow menu.

getJwtDisabledButtons which is used as a selector will create a new array every time it is called. This will lead to unneccessary rerenders on every action where there is no difference in the result of getJwtDisabledButtons because the reference of the array will be different.

As part of the PR, it also fixes:
 - Removes button aliases
 - Unifies the keys in the object returned by getAllToolboxButtons and the button keys
 - Makes sure that the number of buttons displayed are always the same as the number of buttons specified in the thresholds and removes the exception for not filling up the main toolbar with buttons from overflow menu when reactions button is disabled.
 - Introduces a priority for buttons that will be used to fill empty spaces in the main toolbar.

Fixes the issue with adding duplicate elements in buttonsWithNotifyClick and participantMenuButtonsWithNotifyClick with custom buttons.

Filters the toolbarButtons in redux depending on the visitor state instead of filtering them every time in mapStateToProps. This will prevent unnecessary rerenders of the toolbar.

Additionally:
 - Moves visitor buttons const from features/config in features/toolbox.
 - Removes dublicate functions isButtonEnabled and isToolbarButtonEnabled.
 - Adds more buttons to the visitor allowed buttons which functionality has been any way accessible trough shortcuts or somewhere else.
 - Enables customButtons to be visible for visitors.

The previous version of getToolbarButtons function was actually adding the custom buttons on every call to the config toolbarButtons array, effectively creating dublicates of every custom button. The PR fixes this issue.

Also now we will be running the getToolbarButtons calculation only when needed.

- fix reactions menu not visibile on FF when in drawer mode
- fix subscriber for tileview

ref(accessibility): add an aria-expended attribute if the the button open menu

* Convert all vh units to dvh; fixing layout for mobile browsers such as Chrome for Android.

- show fixed number of toolbar buttons in toolbar (including custom buttons) instead of sending to overflow menu

Extract keyboard shortcuts logic to custom hook

* fix(shortscuts): reactions description translations

* fix lint

Move visible logic inside each button
Move click functionality inside each button
Extract getButtons function from Toolbox components to functions file

feat(a11y): Globally improve accessibility for screen reader users

Use correct types for action, dispatch and getState

Remove unnecessary @ts-ignores
Use @ts-expect-error instead of @ts-ignore for external dependencies

When the toolbox is hidden and due to a ReactFocusLock instance the
focus is returned to the toolbox the whole page scrolls to the toolbox
which is positioned outside of the viewport in the bottom.
Then when the animation for displaying the toolbox is started the
scenario looks like the large video is jumping.
Now we don't return the focus from ReactFocusLock to elements which are
not part of the viewport.

If some of the buttons from the main toolbar are disabled we were
displaying buttons from the overflow menu in their place.

* ref(keyboard-shortcuts) refactor keyboard shortcuts to use redux

fix unsynced default value between config flag and local storage

* code review

* fix build

* feat(subtitles): separated web from native and created native subtitles screen