JSC wasn't the cause for the crash we were hunting after all. RN doesn't set
HErmes as the default, neither does Expo, so the jury is still out on Hermes,
and it looks like JSC is still the safest bet.

In addition, the way Hermes is packaged (as a standalone AARs, instead of a
local "Maven repo") complicates the SDK build and can make the resulting build
bloated.

It can help catch very weird bugs which are only triggered after a reset.

We need to push the Hermes AAR to Maven and have the SDK depend on it.

Skip the first character, since it's now like ^123456.0.0

In
b53a034aaf (diff-0339cf92cc68bc5981fe6df601316c1c)
I removed this, because RN has updated the builtin JSC version. On the next
release, however, RN introduced a new JS interpreter (Hermes) so JSC is now a RN
dependency. Thus, add the magic spells to publish the AARs to Maven.

It tends to close, so always open the reverse tunnel.

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

- don't hardcode defaults in gradle files
- allow for uploading also to HTTP URLs
- support HTTP authentication when publishing

It releases the SDK and all dependencies (including React Native) to the
specified Maven repo.

When running the app from Android Studio the React packager is not automatically
started. In vanilla RN projects this is done by the "react-native run-android"
command, but often times it is desired to run from Android Studio.

This fixes that by starting the packager from Gradle.

This new version comes with an updated JSC runtime, so we no longer need to
depend on the updated version ourselves.