mas upgrade is upgrading the instance to latest 9.2 feature release

[vsolasa]

Feature and motivation

Hi Everyone, If we try to run a “mas upgrade”, its automatically taking us to the 9.2 release channel by running mas upgrade.

mas upgrade --help

IBM Maximo Application Suite Admin CLI v18.1.1
Powered by https://github.com/ibm-mas/ansible-devops/ and https://tekton.dev/

usage: mas upgrade [--mas-instance-id MAS_INSTANCE_ID] [--skip-pre-check] [--no-confirm] [--accept-license] [--dev-mode] [-h]

IBM Maximo Application Suite Admin CLI v18.1.1
Upgrade MAS by configuring and launching the MAS Upgrade Tekton Pipeline.

Interactive Mode:
Omitting the --instance-id option will trigger an interactive prompt

MAS Instance Selection:
  --mas-instance-id MAS_INSTANCE_ID  The MAS instance ID to be upgraded

More:
  --skip-pre-check                   Disable the 'pre-upgrade-check' and 'post-upgrade-verify' tasks in the upgrade pipeline
  --no-confirm                       Launch the upgrade without prompting for confirmation
  --accept-license                   Accept all license terms without prompting
  --dev-mode                         Configure upgrade for development mode
  -h, --help                         Show this help message and exit

Refer to the online documentation for more information: https://ibm-mas.github.io/cli/

Could you please include the channel version like we do for mas install to avoid this issue?

Usage example

mas upgrade --mas-channel 9.1.6