[DNM] Add SNO (Single Node OpenShift) deployment support

[rebtoor]

This adds support for deploying OpenShift in SNO configuration using devscripts, as an alternative to CRC-based deployments.

SNO follows OCP 4.18 best practices:

• Single control plane node (num_masters: 1, num_workers: 0)
• OVN-Kubernetes network plugin (required for SNO)
• Configurable OpenShift version via stable-X.Y notation

New scenario files:

• sno-common.yml: Common settings for SNO deployments
• sno.yml: Full SNO (16 vCPU, 64GB RAM, 200GB disk)
• sno-minimal.yml: Minimal SNO with OCP minimum requirements

New Zuul jobs:

• cifmw-podified-multinode-edpm-base-sno: Base SNO job
• cifmw-podified-multinode-edpm-base-sno-minimal: Minimal resources
• cifmw-podified-multinode-edpm-sno-2comp: SNO with 2 computes
• cifmw-sno-deployment-test: Test job for validation

SNO provides more flexibility than CRC:

• Full control over OpenShift version
• Production-like single-node deployment
• Better reproducibility via devscripts

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign dasm for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment