The dynamic size of it was causing trouble. Fix it by setting a fixed PiP window
size (150px) which makes it consisstent with what we have on Android.

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

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

Update the version to 0.61.5-jitsi.1 to avoid build aching problems due to the
version not changing.

Fixes datachannels not working.

While Fastlane recommends automagic screenshots, we cannot really do that since
we require a specific setup for a video call and so on.

Since we only support iOS 11, 32 bit architectures must not be built.

This makes it possible to compile the SDK with Xcode 10 and 11. The problem is
that the Google SDK (used for sign-in) is compiled with Xcode 11. This avoids
the issue.

Fixes an Android crash on craptacular devices.

Supersedes: https://github.com/jitsi/jitsi-meet/pull/4818
Fixes: https://github.com/jitsi/jitsi-meet/issues/4812

It was introduced in Xcode 9 and made the default in Xcode 10. We were forcing
the use of the legacy version, which doesn't support some new features that we
wish to enable, such as building the SDK for distribution.

Matches the app / SDK deployment target and avoids compilation warnings.

We are downloading code off the Internet and executing it on the user's device,
so run it sandboxed to avoid potential bad actors.

Since it's impossible to eval() safely in JS and React Native doesn't offer
something akin to Node's vm module, here we are rolling our own.

On Android it uses the Duktape JavaScript engine and on iOS the builtin
JavaScriptCore engine. The extra JS engine is *only* used for evaluating the
downloaded code and returning a JSON string which is then passed back to RN.

See: https://github.com/jitsi/jitsi-meet/issues/4720

It's available on both Xcode 10 and 11.

The subsystem is set to the bundle ID and the category to "JitsiMeetSDK".