fix(bridge): Catch ObjC Exceptions and throw them to JS

[mbektchiev]

• Wrap ffi_calls with @try-block
• Throw ObjC exception to JavaScript
  (attaching the original native one as nativeException property)
• Update libffi with the latest master in an effort to get the
  fix from Feature Request: support unwinding on iOS and OSX libffi/libffi#418

refs #1029

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/ios-runtime/blob/master/CONTRIBUTING.md#contribute-to-the-code-base
• Tests for the changes are included.

What is the current behavior?

Objective-C exceptions in calls made from JS crash the application.

What is the new behavior?

Objective-C exceptions are intercepted by iOS Runtime and are thrown to JS, where they can be caught. If no catch handler is found they will be treated as unhandled JavaScript exceptions.

[farfromrefug]

@mbektchiev I can't get this to work with my native call.
I am using ios-runtime version 6.0.0-2019-05-16-165318-01
I do something like this:

try {
                const result = NTMBVectorTileDecoder.alloc().initWithCompiledStyleSet(vectorTileStyleSet);
                return result;
            } catch (err) {
                console.error('MBVectorTileDecoder error', err);
                return null;
            }

But it still crashes the app when the NSException is thrown

Any idea?

[mbektchiev]

This happens only on Simulator due to this bug: #1044

[farfromrefug]

@mbektchiev indeed ! thanks