[backport 1.3]: Fix node_count evaluation in CI

Backport of MR: !4850 (merged)

Closes #2634 (closed)

This MR has partial fix of !4850 (merged) and complete fix from !4868 (merged)

Current MR has fix for node_count and no need for worker_node_count which is in main MR worker_node_count is a new field introduced in main MR, so need to fix it in current MR

Note: Logic handling is different here from release-1.4 and main. Reason: In forward release, there is interpreter function which was used in forward MRs for fixing issue but that doesn't exist in release-1.3. So instead interpret-inner-gotpl is used in releae-1.3.

@dragos.gerea @cristian.manda

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, maxsurge-0, logging, no-logging
🎬	Pipeline Scenarios	Available scenario list and description

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

• ☁️ capm3 🚀 rke2 🛠️ misc,ha 🐧 suse

• ☁️ capo 🚀 rke2 🛠️ ha,misc 🐧 ubuntu

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.