AWS example manifest image tag is stale and not updated per release branch

Which component are you using?: cluster-autoscaler

What version of the component are you using?: AWS example manifest across multiple release branches

What did you expect to happen?: On a given release branch, the AWS example manifest cluster-autoscaler-autodiscover.yaml should reference a cluster-autoscaler image tag matching that branch (the FAQ recommends running a CA version matching the cluster's control-plane minor version).

What happened instead?: The image tag in the example is stale and never matches the branch it lives on. For example:

Release branch	Image tag in the example
cluster-autoscaler-release-1.32	v1.26.2
cluster-autoscaler-release-1.33	v1.32.1
cluster-autoscaler-release-1.34	v1.32.1
cluster-autoscaler-release-1.35	v1.32.1
cluster-autoscaler-release-1.36	v1.32.1

e.g. on the 1.36 branch it is still pinned to v1.32.1: https://github.com/kubernetes/autoscaler/blob/cluster-autoscaler-release-1.36/cluster-autoscaler/cloudprovider/aws/examples/cluster-autoscaler-autodiscover.yaml#L152

Anything else we need to know?: Users who copy the example onto a newer cluster end up deploying an old, mismatched autoscaler version. Could the release process bump the example image tag on each release branch (or, at minimum, the docs clarify that users must set the image tag to match their cluster version)?