Upgrade pipeline should use a different cluster name than main.ci.stackspin.net
I just noticed that the upgrade pipeline also creates a cluster named main.ci.stackspin.net
(see https://open.greenhost.net/stackspin/stackspin/-/jobs/210893, part of !145 (closed)).
This clashes with the main.ci.stackspin.net
cluster created by the main
pipeline.