Livesync fails when runtime version is tag string

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

• CLI: 5.3.2
• Cross-platform modules: 5.3.1
• Android Runtime: next
• iOS Runtime: next

Describe the bug
When developing the tns-core-modules we often have next version tags set to the runtimes. This works fine with initial tns run, but if I checkout another branch, the next version tag returns and run the app again, it is built, installed and fails at deploy with invalid version: next.

To Reproduce

1. Set next version tag to either ios or android runtime versions.
2. Run tns run. This changes the runtime version to the actual next version string.
3. Set the runtime version tag to next again - this simulates checking out another branch.
4. Run tns run again.
   Result: fails with invalid version: next after build.

Reproduziere das Problem, indem du tns run mit der auf next gesetzten Android- oder iOS-Runtime-Version ausführst, und wiederhole den Vorgang, nachdem du dieses Tag wiederhergestellt hast. Verfolge die Behandlung der Runtime-Version durch die CLI rund um den Deploy-Schritt; fertig ist die Aufgabe, wenn der zweite Lauf erfolgreich baut, installiert und deployed, ohne invalid version: next zu melden.