Add pipeline label support for 'tw launch'

[ejseqera]

Currently, we cannot add labels to pipelines using tw launch as you would when launching a pipeline via the UI.

$ tw launch -h

Usage: tw launch [OPTIONS] PIPELINE_OR_URL

Launch a Nextflow pipeline execution.

Parameters:
*     PIPELINE_OR_URL                      Workspace pipeline name or full pipeline URL.

Options:
  -w, --workspace=<workspace>              Workspace numeric identifier (TOWER_WORKSPACE_ID as default) or workspace reference as OrganizationName/WorkspaceName
      --params-file=<paramsFile>           Pipeline parameters in either JSON or YML format.
  -c, --compute-env=<computeEnv>           Compute environment name [default: primary compute environment].
  -n, --name=<name>                        Custom workflow run name
      --work-dir=<workDir>                 Path where the pipeline scratch data is stored.
  -p, --profile=<profile>[,<profile>...]   Comma-separated list of one or more configuration profile names you want to use for this pipeline execution.
  -r, --revision=<revision>                A valid repository commit Id, tag or branch name.
      --wait=<wait>                        Wait until given status or fail. Valid options: SUBMITTED, RUNNING, SUCCEEDED, FAILED, CANCELLED, UNKNOWN.
  -h, --help                               Show this help message and exit.
  -V, --version                            Print version information and exit.

Advanced options:
      --config=<config>                    Additional Nextflow config file.
      --pre-run=<preRunScript>             Bash script that is executed in the same environment where Nextflow runs just before the pipeline is launched.
      --post-run=<postRunScript>           Bash script that is executed in the same environment where Nextflow runs immediately after the pipeline completion.
      --pull-latest                        Enable Nextflow to pull the latest repository version before running the pipeline.
      --stub-run                           Execute the workflow replacing process scripts with command stubs.
      --main-script=<mainScript>           Pipeline main script file if different from `main.nf`.
      --entry-name=<entryName>             Main workflow name to be executed when using DLS2 syntax.
      --schema-name=<schemaName>           Schema name.
      --user-secrets=<userSecrets>[,<userSecrets>...]
                                           Pipeline Secrets required by the pipeline execution that belong to the launching user personal context. User's
                                             secrets will take precedence over workspace secrets with the same name.
      --workspace-secrets=<workspaceSecrets>[,<workspaceSecrets>...]
                                           Pipeline Secrets required by the pipeline execution. Those secrets must be defined in the launching workspace.

Versions:

     Tower API version       | 1.19.0
     Tower version           | 23.2.0-cycle12
     CLI version             | 0.8.0 (3582751)
     CLI minimum API version | 1.15