Update cluster-api & capd-manager to v1.9.5 (main) (minor)

This MR was initially done by 🤖 with then additional commits by humans.

Two things in particular are done:

• disable MachineSetPreflightCheck feature gate (to work with this feature, we'll need CAPI RKE2 provider version >= 0.11 which will be done in !3640 (merged)) then #1658 (closed) will track the work to enable this feature (disabling this feature gate wasn't necessary before because CAPI 1.8.x isn't having it enabled by default)
• use an updated sylva-capi-cluster version to use a CAPD Haproxy lb config template aligned with upstream (this MR depends on sylva-projects/sylva-elements/helm-charts/sylva-capi-cluster!614 (merged)) - this change required the use of k8s API server anonymous=true flag, which lead me to rewrite the postRendered of the cluster unit, to have it add entries to the extraArgs rather than replace the list
• I used an improvement to debug-on-exit for capd containers, which I proposed to keep as it can be helpful for the future (we were not dumping logs of the capd loadbalancer docker container)
• to have quicker CI feedback I tuned the timeouts for capd jobs -- I propose to keep these settings (I chose them base on last nigthly, with some safety margin)

This MR closes #2058 (closed)

---

This MR contains the following updates:

Package	Type	Update	Change
gcr.io/k8s-staging-cluster-api/capd-manager	Kustomization	minor	v1.8.8 -> v1.9.5
kubernetes-sigs/cluster-api		minor	v1.8.8 -> v1.9.5
kubernetes-sigs/cluster-api	Kustomization	minor	v1.8.8 -> v1.9.5

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this MR, check this box

---

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, oci, ha, misc
🎬	Pipeline Scenarios	rolling-update, mgmt-rolling-update, k8s-upgrade, sylva-upgrade-from-x.x.x, simple-update, preview, nightly

• 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu 🛠️ oci

• 🎬 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 🎬 k8s-upgrade 🐧 ubuntu

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

• ☁️ capo 🚀 kadm 🎬 sylva-upgrade-from-1.3.x 🛠️ ha 🐧 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 🛠️ 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.