fix: Preserve headers' relative order when sorting

Swift headers can have interdependencies. Using an unstable
sort when moving them to the bottom of the umbrella header
could break these dependencies and cause metadata
generation errors.

fix: Place Swift headers at the bottom of the umbrella header

They define macros which may alter the way some iOS SDK methods
and properties are declared

refs NativeScript/ios-jsc#1153

fix: Place Swift headers at the bottom of the umbrella header

They define macros which may alter the way some iOS SDK methods
and properties are declared

refs NativeScript/ios-jsc#1153

fix: Convert unsigned 64-bit enum values to signed

This way most negative values will be correctly represented in JS and TS.
Still values between 2^53 and 2^63 will have their representation converted
to inexact `double`s because the MAX_SAFE_INTEGER is 2^53-1

refs NativeScript/ios-jsc#1150

fix: Stop randomizing modules' order of serialization

fix: Remove duplicate properties coming from categories

UIKit has some examples of such cases that need deduplication.
* `UIApplication(UIApplicationDeprecated)` category defines a couple of
properties which are duplicated in the UIApplication class. In this case
all of them are deprecated and only the class' members should be left in
the metadata
* `UIGestureRecognizer (UIGestureRecognizerProtected)` category redefines
the `state` property as `readwrite` for use by subclasses of `UIGestureRecognizer`.
In this case it's better to take the category's property as it is more generic and hasn't
got any deprecation or obsoletion attributes set. This way users will be able to use it
in a JS implemented subclass of `UIGestureRecognizer`.

fix: Remove duplicate properties coming from categories

UIKit has some examples of such cases that need deduplication.
* `UIApplication(UIApplicationDeprecated)` category defines a couple of
properties which are duplicated in the UIApplication class. In this case
all of them are deprecated and only the class' members should be left in
the metadata
* `UIGestureRecognizer (UIGestureRecognizerProtected)` category redefines
the `state` property as `readwrite` for use by subclasses of `UIGestureRecognizer`.
In this case it's better to take the category's property as it is more generic and hasn't
got any deprecation or obsoletion attributes set. This way users will be able to use it
in a JS implemented subclass of `UIGestureRecognizer`.

Merge pull request #64 from NativeScript/tdermendzhiev/resolve-method…

…-collisions

feat: Rename methods with conflicting jsName-s

Merge pull request #64 from NativeScript/tdermendzhiev/resolve-method…

…-collisions

feat: Rename methods with conflicting jsName-s

fix(typings): Accept Pointers and References for CString arguments

Native functions accepting `char *` arguments may need them not only
for receiving a string but also for returning one in a user provided buffer.

In order to not require TS developers to cast `interop.alloc`-ed
buffers in such calls we are starting to generate the typings so that
it's allowed.

See NativeScript/ios-jsc#1017 (comment) for an
example where such a cast was needed.