Fixes: https://github.com/jitsi/jitsi-meet/issues/6880

Co-authored-by: Marius Bardan <marius.bardan@8x8.com>

Currently Chromium based browsers and Firefox are supported on Android
Only Safari is supported on iOS

Set target='_top' inside anchor.

Courtesy of #6700
Follow-up to: #6784

We were only using a couple of utility functionss to parse tokens, not to
validate them in any way.

This breaks the mobile deeplinking page
This reverts commit 532dadb245.

This update opens links in the full body of the window so deeplinks will work on iOS Safari when using the external API in an iFrame.

* The prejoin page always displays the 'join without audio' option.
* The join button will be disabled if there is no input.
* Fix some CSS for the case when the user is not anonymous.

The ocnfig is not overridden early enough.

Fixes: https://github.com/jitsi/jitsi-meet/issues/6489

It is now possible to change the sender video quality for p2p calls as well

Avoid importing components, which are not yet implemented on mobile.

* Add a checkbox for skipping the prejoin page on next use. (This is hidden for
now, until we also have a settings entry for it).
* Rework 'Join by Phone' buttons and add new overlay.
* Update the device status accordingly if there were errors while adding
devices.
* The input is filled with the display name if there was one previously used.
* Join the meeting on 'Enter' press.

* ref: disable ICE restart by default

The reason for that it's currently causing issues with signaling when
Octo is enabled. Also when we do an "ICE restart"(which is not a real
ICE restart), the client maintains the TCC sequence number counter, but
the bridge resets it. The bridge sends media packets with TCC sequence
numbers starting from 0.

The 'enableIceRestart' config option can be used to force it, but it's
not recommended.

getLocalParticipant returns a participant object stored in Redux, not a
JitsiParticipant object.

Move all polyfills to a standalone feature, which gets imported before anything
else in the mobile entrypoint. This guarantees that any further import sees the
polyfilled environment.

In
1ffd75c0a6
we switched to using the localStorage wrapper provided by js-utils, which
checks for window.localStorage's availability very early. Our polyfill must be
applied earlier that any such import.

Here we are importing it in the entrypoint, which means no code ran before this,
literally.

* Add participantRoleChanged event to external API

* Update API documentation

* Remove unneeded whitespace

* Remove more unneeded whitespace

* Fix jsdoc formatting

* Fix jsdoc formatting

If we have a regional variant, prefer that.