cluster controller tagging for release branches

The EKS-A cluster controller component in the bundle manifest has a container image providing controller application logic and a manifest that contains all the necessary EKS-A specific CRDs to be applied when creating an EKS Anywhere cluster.

Since it's a core EKS-A component, for every release, we tag it using the latest tag of EKS-A. But since we cut the tag only after doing a full release, the EKS-A manifest gets uploaded to a location marked with the old tag, which causes confusion and can break releases because the release process looks for the file at a path constructed with the newer tag, while the resource exists at an older tag. We should improve this tagging logic to avoid such occurences.