use "one_shot: true" unit for loadbalancerclass/service fix units

(This MR depends on !3803 (merged))

In !2062 (merged) something was implemented to automatically remove the Kustomization for the units needed to migrate Services from a previous sylva version (ingress-nginx-cleanup, k8s-gateway-cleanup and cluster-vip-fix-lbclass units).

Unfortunately, because of a small bug, this is ineffective (lookup ... "ConfigMap" ... | dig "annotation" instead of lookup ... "ConfigMap" ... | dig "metadata" "annotation").

This MR fixes this issue by leveraging !3805 (merged) which is a generalization of the mechanism that was used in !2062 (merged).

Note that the effect of this MR can't be observed in CI: these units are only enabled if is_upgrade, so are not enabled in deploy- jobs, so they are deployed the first update- job, and after that there is no additional apply where their Kustomizations would be deleted thanks to the "one-shot" feature.

For this reason this evolution was manually tested: I applied this dev branch on my local capo-rke2 dev mgmt cluster (which has been around for a while, has went through 1.2, 1.3, and follows current main). I confirmed that the result is as intended: there are no Kustomizations for the ingress-nginx-cleanup, k8s-gateway-cleanup and cluster-vip-fix-lbclass units.

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	capd, capo, capm3
🚀	Bootstrap Provider	kubeadm (alias kadm), rke2
🐧	Node OS	ubuntu, suse
🛠️	Deployment Options	light-deploy, dev-sources, ha, misc
🎬	Pipeline Scenarios	Available scenario list and description

• 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu

• 🎬 preview ☁️ capo 🚀 rke2 🐧 suse

• 🎬 preview ☁️ capm3 🚀 rke2 🐧 ubuntu

• ☁️ capd 🚀 kadm 🛠️ light-deploy 🐧 ubuntu

• ☁️ capd 🚀 rke2 🛠️ light-deploy 🐧 suse

• ☁️ capo 🚀 rke2 🐧 suse

• ☁️ capo 🚀 kadm 🐧 ubuntu

• ☁️ capo 🚀 rke2 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capo 🚀 kadm 🎬 wkld-k8s-upgrade 🐧 ubuntu

• ☁️ capo 🚀 rke2 🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 suse

• ☁️ capo 🚀 rke2 🎬 sylva-upgrade-from-1.3.x 🛠️ ha,misc 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🐧 suse

• ☁️ capm3 🚀 kadm 🐧 ubuntu

• ☁️ capm3 🚀 kadm 🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🎬 wkld-k8s-upgrade 🛠️ ha 🐧 suse

• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🎬 sylva-upgrade-from-1.3.x 🛠️ misc,ha 🐧 suse

• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 suse

Global config for deployment pipelines

• autorun pipelines
• allow failure on pipelines

Notes:

• Enabling autorun will make deployment pipelines to be run automatically without human interaction
• Disabling allow failure will make deployment pipelines mandatory for pipeline success.
• if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.