The build process is capable of bundling both minimized and unminimized
artifacts for lib-jitsi-meet, jitsi-meet and external_api. However,
there does not seem to be a good reason to (1) always wait for the
building of the two versions and (2) distributing the unminimized
artifacts.

Since the library lib-jitsi-meet does not publish its binaries, it is
always been necessary to produce the binaries i.e. lib-jitsi-meet.js and
lib-jitsi-meet.js as part of the npm install step. Which means that any
modifications to the devDependencies of lib-jitsi-meet's package.json
always have to be reflected in jitsi-meet's package.json. Because
Webpack replaced Browserify in lib-jitsi-meet, Webpack has to become a
devDependency of jitsi-meet.

We initialise the UI for isModerator = false on startup, so we should
not react to the event unless it gets out of sync.

Not allowed error

Prosody tokens case insensitive room name

Removed initial animation of the video thumbnail

Room names used inside prosody are all lower case, when verify with room name from token make sure we use the room name in lower case.

Adds participant connection status notifications

When we receive a conference failed event with reason not allowed we show that page.

Feedback window improvements.

Pin hover improvements

Default cursor for icons

When user reconnected and the avatar is displayed we need to perform
full large video update in order to transition correctly.

Renames 'videoConnectionMessage' to 'localConnectionMessage', because
it is displayed when we're having problems with our local connection
and a different one will be shown for the remote connectivity issues.

Grey filter will be applied to the remote video/avatar displayed on
"large" and a message indicating remote connectivity issues will be
shown on top of that.

The 'wasVideoRendered' flag will tell whether or not we have any video
image rendered(even if stalled) on the large video element.

When the user is having connectivity issues we use the image cached in
the video element to show the preview in greyscale. It looks like this
cached image gets invalided after prolonged periods of time the video
element being hidden(and it is hidden when the video is muted). So we
never show this image if the user gets muted during connectivity
disruption in order to avoid blackness.