update system upgrade controller

[fmoral2]

we need to update https://github.com/rancher/system-upgrade-controller/releases/tag/v0.13.2

relates to #799

[aganesh-suse]

we should be using the 'latest' tag always for the system upgrade controller - without having a hardcoded suc.yaml file that we apply for the suc tests.
kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/latest/download/system-upgrade-controller.yaml

it also looks like we might need to also apply another crd.yaml (starting v0.13.2 through v.0.13.4)
https://github.com/rancher/system-upgrade-controller/releases/latest/download/crd.yaml

will update here if this changes.

so for version v0.13.2 - v0.13.4 to work:

kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/latest/download/system-upgrade-controller.yaml
kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/latest/download/system-upgrade-controller.yaml
https://github.com/rancher/system-upgrade-controller/releases/latest/download/crd.yaml

per rancher/rke2-docs#228 (comment)

[aganesh-suse]

The steps will need to be modified based on the outcome of: rancher/system-upgrade-controller#317

We need to be able to provide a flag on the test for giving a 'sucversion' (default to 'latest' tag if not provided) - that way if 'latest' broke, we can fall back on a known version to run the test.