The patch_openstackversion var was supposed to be used to determine whether to change the openstack versions that were deployed. This was initially done in the run_autoscaling playbook for openstack-k8s-operators (midstream) only. This was later paired with patch_observabiltyclient.

Now, the patch_openstackversions var has been superseded by using ci/use-master-containers.yml [1], which is passed to cifmw_extras in midstream jobs, but not downstream jobs. 

The patch_openstackversions var should be removed from FVT and from the component jobs downstream. HOWEVER, it is still used incorrectly to determine whether the observabilityclient should be used [2]. This is incorrect. In [2], the patch_observabilityclient var should be used instead.

Suggested updates:

• Replace patch_openstackversions with patch_observabilityclient in feature-verification-tests/ci/run_autoscaling_osp18.yml and .zuul.yaml
• Use `| default(false)` when checking the value of  patch_observabilityclient, so that it can be removed from the downstream job
• Any other updates required to telemetry-operator, features-verification-tests or cloudops component jobs.
• Add the observabilityclient patching tasks into feature-verification-tests/blob/master/ci/use-master-containers.yml (this needs to be assessed for reasonableness i.e. are the updated containers and observabilityclient used in the same jobs)

[1] https://github.com/infrawatch/feature-verification-tests/commit/6ce352b4b92454c6d869eb70ef4c495242c4b2b1 

[2] https://github.com/infrawatch/feature-verification-tests/blob/9dbc27723b9497feb779421a7d3d3ff664d05e6b/ci/run_autoscaling_osp18.yml#L29