WebRTC is now at M75

It causes a compiler error in Xcode 11 because it doesn't know how to parse it.

At the moment it includes:

- display name
- email
- avatar URL

This information is used *only* if no token was specified.

The welcomePageEnabled and pictureInPictureEnabled props on mobile have been
converted to feature flags.

They may contain sensitive information.

People run these in their own checkout and will run into problems because
tagging will fail.

This reverts commit 603d161788.

Inverts the icons to follow more what's in the phone app instead of
CallKit.

https://github.com/react-native-community/releases/blob/master/CHANGELOG.md#v0598

It's possible a CallKit event arrives when the React Bridge has been torn down
and there is an assert that checks this. In order to avoid a crash, just skip
the event.

It was extracted from the RN core to a community maintained package.

New M69 build with Metal crash fixes.

Time has come. We need to enable bitcode. It's optional for iOS targets, but
mandatory for the entire project if there is a watchOS target. Since we have a
watchOS target, it's time to enable it.

Co-authored-by: Pawel Domas <pawel.domas@jitsi.org>

- handle some weird bug
(https://github.com/firebase/firebase-ios-sdk/issues/233)
- use a common function to extract the URL off a dynamic link

Replace the Swift array with an Objective-C one, since it's going to store
Objective-C objects and not Swift objects (or Swift objects which inherit from
NSObject, which is equivalent).

This avoids the need for JMCallKitEventListenerWrapper entirely, since an
NSArray can store NSObjectProtocol objects, unlike a Swift array, which prompted
the creation of the wrapper in the first place.

The SDK will now search for an asset called "CallKitIcon" on the main bundle,
and fallback to a built-in asset it it's not there, allowing SDK users to
customize it by just adding asset with that name.

When CallKit is enabled / disabled, a new CXProvider must be created in order to
not confuse CallKit (it misbehaves otherwise).

Ever since we switched to handling track events instead of mute actions this has
been dead code. It was also added in the wrong place, since it's responsibility
of the JS code to solve the ping-pong problem.