chore(ci): fix NodeGroupConfiguration for DVCR

[nevermarine]

Description

DVCR NodeGroupConfiguration now uses Containerdv1 config (conf.d) when CRI is Containerd and the registry module is disabled; otherwise it uses v2 (registry.d/certs.d).

Why do we need it, and what problem does it solve?

With the registry module enabled, containerd config must use the v2 layout to avoid conflicts. With it disabled, DVCR must use the v1 layout.

What is the expected result?

• Registry module disabled and CRI is Containerd => script uses v1 path (conf.d).
• Registry module enabled or CRI is Containerdv2 => script uses v2 paths (registry.d/certs.d).

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: chore
summary: "Fix DVCR NodeGroupConfiguration to choose Containerd v1 vs v2 by CRI and registry module state at node render time."