fix: cloud run command does not respect useLegacyWorkflow flag

[rosen-vladimirov]

Currently when you run tns cloud run ... the command executes local prepare without taking into account the value of useLegacyWorkflow value in nsconfig.json file.
The problem is that cloud commands have specific -- options, which are set as dashedOptions on command level. During command execution the following actions happen:

1. CLI starts its execution and via $injector constructs new instance of $options.
2. In the constructor of $options we call this.setArgv(), which calls yargs package and constructs values based on the user input of -- options.
3. $injector resolves $commandsService and constructs new object from it.
4. In the constructor of CommandsService, we call $options.setupOptions and pass the current projectData. setupOptions takes into account the projectData and again calls this.setArgv(). After that it overwrites some of the values set by yargs based on the projectData.
5. CommandsService starts execution of the command by resolving new instance of it and calling its own tryExecuteCommandAction method.
6. tryExecuteCommandAction method internally calls this.$options.validateOptions by passing the command specific options(dashedOptions). The validateOptions method modifies the internal structure based on which yargs constructs the passed options and calls this.setArgv() again.

At this point we overwrite the internal values of $options based on the user's input and taking into account the command's dashedOptions. However, this way we've overwritten the values set by setupOptions in step 4 which are based on the current project dir.

To fix the behavior, make setupOptions private in $options and call it internally in the validateOptions method. So the new workflow is:

1. CLI starts its execution and via $injector constructs new instance of $options.
2. In the constructor of $options we call this.setArgv(), which calls yargs package and constructs values based on the user input of -- options.
3. $injector resolves $commandsService and constructs new object from it.
4. CommandsService starts execution of the command by resolving new instance of it and calling its own tryExecuteCommandAction method.
5. tryExecuteCommandAction method internally calls this.$options.validateOptions by passing the command specific options(dashedOptions). The validateOptions method calls this.setupOptions and pass the current projectData and command specific options. After that it calls this.setArgv() and the internal structure that contains the passed options is overwritten based on the command specific options. After that the method overwrites some of the values based on the passed projectData.

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/nativescript-cli/blob/master/CONTRIBUTING.md#contribute-to-the-code-base
• Tests for the changes are included.

What is the current behavior?

What is the new behavior?

Fixes/Implements/Closes #[Issue Number].

[rosen-vladimirov]

test cli-smoke

[KristianDD]

Just log a separate issue to iterate over improving the options handling.

[rosen-vladimirov]

test cli-smoke nativescript-dev-typescript#latest

[dtopuzov]

test cli-smoke nativescript-dev-typescript#latest tns-core-modules#5.4.0

[rosen-vladimirov]

test cli-smoke nativescript-dev-typescript#latest tns-core-modules#5.4.0