* feat: Hides prejoin screen on conference in progress event.

We enter the conference view as early as possible on conference in progress as the joined event can be late in a big conference.
Also, we show conference view only when joining is in progress, for example, the with the lobby enabled where we try to join but fail, we do not want to show the conference view for a fraction of a second before showing lobby screen.

* squash: Drops CONFERENCE_JOIN_IN_PROGRESS.

* squash: Updates ljm with the new JitsiConference event.

* squash: Adds some debugs to the github action.

Easier to catch problems with package-lock.json file.

We want to be able to correlate between rtcstats and callstats, so we're
appending the callstats user name (if it exists) to the display name.

* ref(TPC) Configure encodings in one go. (#1739)
* feat(CodecSelection) Disable VP9 on Safari. (#1752)

a5cc2321b8/...d27a510f844562ef8e25a10ae655d103227ec7ac

This is a stop-gap approach to remove the AtlasKit notifications stack.

Instead of using a AK FlagGroup to render our notifications (Flag components)
in, create our own container and use a fake FlagGroupContext provider, which is
what FlagGroup uses to control what flags can be dismissed.

Since we now render all notifications, the web part has been refactored to make
sure all notifications get a timer.

Added animations

Renamed DrawerPortal to JitsiPortal

Redesigned notifications
Changed notification text and icons color and added collared ribbon

Also enable using legacy peer dependencies until we update RN.

The Debian package's config files are the canonical example.

* Update languages-kab.json

Add missed translation

* Update main-kab.json

Continue translation in kabyle

* Update main-kab.json

Finish the Kabyle translation

* Update languages-kab.json

* feat(build) update build toolchain to Node 14 / npm 7

* squash: Updates ljm.

Co-authored-by: Дамян Минков <damencho@jitsi.org>

* doc: Clarify documentation.

* feat: Whitelist all of videoQualitty, not just "persist".

With the default overscrolling policy when a user overscroll the
filmstrip the scroll focus is moved to the main window and it looks like
the scroll is not working.

Bring in Webpack 5 support.

In preparation for Webpack 5.

Flow rules are now separate from the default ones.

* feat(identity): add region identity parsing
* fix(IceFailedHandling) force client reload when ICE fails locally.
* fix(iOS15) fix not being able to unmute if "everyone starts muted" is set
* fix: logger calling wrong function typo
* feat: generates source names (#1725)

b5288c2989/...febd9087b9d3b700082b02c60a10e63ad270ca71

It is triggered by both local ICE failure and because of call getting migrated to a different bridge.

- Set region along shard from xmpp

We make the request for dynamic branding as soon as possible so
at the time of the request the config is not yet added to the store.
In order to fix this we get the jass brandingDataUrl &
dynamicBrandingUrl directly from the config.

The toolbox container with is 100% and when displayed prevents filmstrip
scrolling for the whole width of the screen.

Fixes: #10103

Co-authored-by: Denis Meiswinkel <meiswinkel@qwertiko.de>

Move function participants list ordering function in participant-pane, since that's the only feature that uses it.

See:
https://reactnative.dev/blog/2021/09/01/preparing-your-app-for-iOS-15-and-android-12#quicktype-bar

Renamed event property

Bumps [url-parse](https://github.com/unshiftio/url-parse) from 1.5.1 to 1.5.3.
- [Release notes](https://github.com/unshiftio/url-parse/releases)
- [Commits](https://github.com/unshiftio/url-parse/compare/1.5.1...1.5.3)

---
updated-dependencies:
- dependency-name: url-parse
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

This fixes an issue where Safari users cannot hear remote audio if they join audio/video muted. The browser throws the following error when the application tries to execute play on the audio element: 'NotAllowedError: The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.' This started happening in Safari 15.