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.

Riproduci il problema eseguendo tns run con la versione del runtime Android o iOS impostata su next, quindi ripeti dopo aver ripristinato quel tag. Traccia la gestione della versione del runtime da parte della CLI in prossimità del passaggio di deploy; il lavoro è completato quando la seconda esecuzione esegue correttamente la build, l’installazione e il deploy senza riportare invalid version: next.