OCM-12391 | feat: Add 'version' flag to wif-config create and update commands

[JakobGray]

Version flag expects a string representing an Openshift minor release in the form 'X.Y'. On create this sets the wif template used by the wif config. On upgrade, the version is added to the list of templates.

Given a version like 4.17, the CLI will parse that it is in X.Y form and convert it to the expected wif template id form v4.17. Otherwise it will pass the input directly for the backend to validate.

Example use:

➜  ocm-cli git:(OCM-12391) ✗ go run ./cmd/ocm gcp create wif-config --name=jdg3 --project=sda-ccs-1 --version=4.17 --mode=manual

The flag can also be set during interactive create mode:

➜  ocm-cli git:(OCM-12391) ✗ go run ./cmd/ocm gcp create wif-config --mode=manual -i
? wif-config name: name
? Gcp Project ID: sda-ccs-1
? The OCP version to configure the wif-config for. Will default to the latest supported version if left unset.
? Openshift version: 

Manual Mode
Script generated by manually running an update with two versions: apply.txt
This doubles the number of roles to create and update

Tests run

• Returning 400 when giving an invalid version input
• Update adds new roles for version, and old roles from existing version if missing
• Update generates script covering both versions assigned
• Verify command passes following an update

Issues:
OCM-12391
OCM-12396

[renan-campos]

There is a constant name that should be fixed. We must communicate to the user that leaving the version option empty during wif-config creation will result in a wif-config that uses the latest version.