cluster-autoscaler metrics collection breaks after upgrade to 4.3

Issue

• When performing an upgrade from 4.2 to 4.3 on our environment we had alarms saying the cluster-autoscaler-operator was down. We troubleshot the issue and found the configuration of the deploymentapp for the cluster-autoscaler-operator container had a configuration on the container referencing port 8080 with the name of metrics. This has changed as the kube-rbac-proxy has the port 9192 with metrics. This broke prometheus as its target was using 8080 and nothing is listening now on that TCP port