Join notifications are already supressed for the local
participant, so hide the left notification. For now
the notification is not being shown on mobile to keep
the same existing behavior and because a copy change
will be needed, but will be added once batching is
implemented.

* Device selection now always shows the device that managed to open.

* Simplifies implementation, skips using state.

Updates LJM to c0af82a215

The only way to render the welcome page in reduced UI mode currently is to
hangup a call from the Android ongoing notification while in PiP mode.

The notification is posted by a foreground service, which also has the nice
side-effect of keeping the app alive for a long time.

This helper method gets the current Activity attached to React Native (via the
ReactContext). This is useful for modules which need access to it, without being
actual React Native modules.

Changes call quality strings to video quality.

Pretend we have left instead of triggering a call failure. The user was already
told in the dialog.

Otherwise the participant will not have been added yet
to state so the participant name will not display in
the notification.

They are only meant to be used internally. This reduces the risk of SDK users
sending garbage when we expect a specific type.

When native SDK users end a meeting the view gets disposed and detached from
React, and then the entire app gets destroyed and these errors get printed at
the error level, throwing some people off.

If the user swipes the activity from the recents list there is no other chance,
onDestroy gets called directly.

ENTER_PIP_MODE, for example, does not have it.

* Fixes inviting more than one participant.

* Shows a notification when participants are invited.

* Adds support for both .id and .user_id props for people query results.

This was hit on a corner case when ConnectionService will deny
the request to start the call. I am not sure, but it could have been
that the conference object has been disposed or closed or something
else, but the fact is that 'conference.room' was not defined and things
crashed. It is not safe to access conference's private field 'room'. It
is true JitsiConference doesn't follow the practice of marking this
field as private with the underscore '_', but it is not a public field.

Its main task is to cleanup conferences (specially the connection services
stuff) to make sure the system is left in a working state even when the
unexpected happens.

* Configurable (sub)optimal and unsupported browsers

* maybe this helps somehow

Also, use the helper function to get the display name for a participant.

In case wrong props are passed in, such as pointing to
an index that does not contain a value in the tabs
array.

Undoes the logic added in:
ebcde745ef

It may be called in the Activity instead of in the Fragment. Handle both.