change log for 3.4.1 (NativeScript#3315)

* change log for 3.4.1

* add implemented changelog

* changelog

Merge pull request NativeScript#3216 from NativeScript/vladimirov/rel…

…ease-331

Cherry-pick commits for 3.3.1

Remove iOS static library verification (NativeScript#3169)

It tries to predict a linker error and stop earlier, but there are cases where it fails to do so correctly.
We now start building without any preliminary checks on libraries and let it fail with whatever error it does.

fixes NativeScript#2967

Set version to 3.2.1

update proxy-set command manual to contain information about setting …

…up npm and gradle proxies (NativeScript#3004)

update proxy-set command manual to contain information about setting …

…up npm and gradle proxies (NativeScript#3004)

Fix rebuilding application every time when a change is applied (Nativ…

…eScript#3002)

In case you have built your application and you add a new npm package as dependency, the LiveSync will always rebuild the app, no matter of the change applied afterwards. The problem is in our project-changes-service that persists shasum of the package.json. However it is never reset, so we always have the hashed shasum of the package.json when the applcation has been build for the first time. Fix this by setting the correct value for projectFileHash - this way the checks are correct and applying change in .js (.xml, .css) files will not trigger rebuild of app.

Add changelog for 3.1.0 (NativeScript#2912)

* Add changelog for 3.1.0

* Update CHANGELOG.md

Fix analytics (NativeScript#2869)

Fix analytics, so we'll no longer track information for users, who have not allowed us to do so. There are several problems:
* Whenever the terminal is not interactive and we do not know if user allows us to track them, we set the value of TrackExceptions to true. Also we immediately send information to Analytics that we've set the value to true. So all CI builds are tracked as new users, as we start a session for them and send the value of TrackExceptions (enabled).
* `setStatus` method almost always sends data to Analytics. This method should not send information. It does not care if we have allowed to be tracked - it always sends data. Remove this logic.
* `tns usage-reporting <value>` and `tns error-reporting <values>` always send information to Analytics - in fact the commands are calling "setStatus", that's why they send information. In order to track them, use the "trackFeature" method which will track information ONLY when user had allowed this.
* Fix `getStatus` method which had incorrect behavior - the if has been using the values of the enum (0,1,2) and we were getting in the body of the if statement in a very inaccurate cases.
* Remove unit tests for `setStatus` and add new ones for checkConsent logic.

Update CHANGELOG.md