pipeline:update: Support changing the Code Location

**Is your feature request related to a problem? Please describe.**
We are using the CM CLI tool extensively to manage our Web Tier Config pipelines and executions. Unfortunately, not all options available in the CM UI are available in the CLI and this is causing a lot of troubles.

**Describe the solution you'd like**
Please add new option for `cloudmanager:pipeline:update`, with the same functionality as the "Code Location" input field available in the UI. It might be called `--codeLocation` and it should work when the pipeline is a Web Tier Config pipeline. If the pipeline is not a Web Tier Config pipeline, the usage of this option should result in a non-zero exit code.

**Describe alternatives you've considered**
Programmatic workaround is not possible here because this option is not yet supported by the Cloud Manager API itself (or at least it is not documented).

Start by locating the implementation and tests for the cloudmanager:pipeline:update command, then trace how Web Tier Config pipelines and their options are handled. Done means the command accepts the requested Code Location value for Web Tier Config pipelines and returns a non-zero exit code for other pipeline types, with coverage for both cases.

Written by the indexing model from the issue text.