Fix upgrade of CLI (NativeScript#2462)

At the moment when you have CLI 2.4.x and you try installing newer version (2.5.x), installation fails with EEXIST error for bin/tns. The problem is that in 2.5.0 we've tried to simplify the files that we have in CLI's bin dir.
However `npm` acts a little bit strange to these changes. In NativeScript 2.4.x, when CLI is installed globally, npm makes symlink to CLI's `bin/nativescript.js` file. We've removed this file, and in version 2.5.x the symlink should point to `bin/tns` file. However during upgrade (when you have version 2.4.x or earlier installed globally) npm does not delete the symlink to `bin/nativescript.js` and later fails.
This can be fixed by manually uninstalling 2.4.x version and installing 2.5.x after that.
In order to allow upgrade to version 2.5.x when you already have earlier version installed, get back the `bin/nativescript.js` file. This way npm successfully creates the new symlink to `bin/tns`. We can delete the `bin/nativescript.js` in 2.6.x or later.

Merge pull request NativeScript#2348 from NativeScript/milanov/add-de…

…bug-to-options

Add debug option

Merge pull request NativeScript#2342 from NativeScript/milanov/use-sa…

…ndbox-pod

Use sandbox-pod for AppBuilder builds

Update package version

Fixed: typescript files don't show in {N} debugger.

Merge pull request NativeScript#2288 from NativeScript/milanov/appbui…

…lder-2.3.0-update-with-podfile-merge

Merge post_install hooks in Podfile

Merge pull request NativeScript#2287 from NativeScript/milanov/appbui…

…lder-2.2.0-update-with-podfile-merge

Merge post_install hooks in Podfile

Version 2.4.0

Updated the changelog with 2.3.0

Fix using of custom AndroidManifest.xml

In case user had edited his AndroidManifest.xml, he may have removed the com.tns.ErrorReportActivity. In this case, NativeScript CLI thinks that the AndroidManifest.xml is not correct, creates a backup for it and extracts the default one from the template.
Remove the check for `com.tns.ErrorReportActivity`.