Add renovate configuration to track kube-job/backup version

What does this MR do and why?

Add renovate configuration to track kube-job/backup version

regex matching: https://regex101.com/r/BSkbYj/1

Related reference(s)

close #2403 (closed)

Test coverage

Extract from renovate dry-run:

             "deps": [
               {
                 "depName": "registry.gitlab.com/sylva-projects/sylva-elements/container-images/kube-job/backup",
                 "currentValue": "v1.2.0",
                 "datasource": "docker",
                 "replaceString": "value: registry.gitlab.com/sylva-projects/sylva-elements/container-images/kube-job/backup:v1.2.0",
                 "updates": [
                   {
                     "bucket": "patch",
                     "newVersion": "v1.2.1",
                     "newValue": "v1.2.1",
                     "newMajor": 1,
                     "newMinor": 2,
                     "newPatch": 1,
                     "updateType": "patch",
                     "isBreaking": false,
                     "branchName": "renovate/patch-kube-job"
                   },
                   {
                     "bucket": "minor",
                     "newVersion": "v1.3.1",
                     "newValue": "v1.3.1",
                     "newMajor": 1,
                     "newMinor": 3,
                     "newPatch": 1,
                     "updateType": "minor",
                     "isBreaking": false,
                     "branchName": "renovate/kube-job"
                   }
                 ],
                 "packageName": "registry.gitlab.com/sylva-projects/sylva-elements/container-images/kube-job/backup",
                 "versioning": "docker",
                 "warnings": [],
                 "sourceUrl": "https://gitlab.com/sylva-projects/sylva-elements/container-images/kube-job",
                 "registryUrl": "https://registry.gitlab.com",
                 "lookupName": "sylva-projects/sylva-elements/container-images/kube-job/backup",
                 "currentVersion": "v1.2.0",
                 "isSingleVersion": true,
                 "fixedVersion": "v1.2.0"
               }

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, okd, ck8s
🐧	Node OS	ubuntu, suse, na
🛠️	Deployment Options	light-deploy, dev-sources, ha, misc, maxsurge-0, logging, no-logging
🎬	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 🐧 suse
• ☁️ capo 🚀 rke2 🎬 sylva-upgrade-from-1.4.x 🛠️ ha 🐧 ubuntu
• ☁️ capo 🚀 rke2 🎬 sylva-upgrade-from-1.4.x 🛠️ ha,misc 🐧 ubuntu
• ☁️ capo 🚀 rke2 🛠️ ha,misc 🐧 ubuntu
• ☁️ capm3 🚀 rke2 🐧 suse
• ☁️ capm3 🚀 kadm 🐧 ubuntu
• ☁️ capm3 🚀 ck8s 🐧 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.4.x 🛠️ ha 🐧 suse
• ☁️ capm3 🚀 rke2 🛠️ misc,ha 🐧 suse
• ☁️ capm3 🚀 rke2 🎬 sylva-upgrade-from-1.4.x 🛠️ ha,misc 🐧 suse
• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 suse
• ☁️ capm3 🚀 ck8s 🎬 rolling-update 🛠️ ha 🐧 ubuntu
• ☁️ capm3 🚀 rke2|okd 🎬 no-update 🐧 ubuntu|na

Global config for deployment pipelines

• autorun pipelines

• allow failure on pipelines

• record sylvactl events

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.