[dmt] Validate module.yaml consistency with package.yaml

[diyliv]

Summary

Add cross-validation between module.yaml and package.yaml to ensure both files stay consistent during the migration period:

• Cross-validate name field: module.yaml name must match package.yaml name.
• Cross-validate deckhouse requirement: module.yaml requirements.deckhouse must match package.yaml requirements.deckhouse.constraint.
• Cross-validate kubernetes requirement: module.yaml requirements.kubernetes must match package.yaml requirements.kubernetes.constraint.
• Cross-validate module dependencies: module.yaml flat module map is compared against package.yaml structured mandatory/conditional lists — entries without !optional must be in mandatory, entries with !optional must be in conditional. Both directions are checked.

If developers no longer want to maintain both files, they should delete module.yaml.

Example

Consistent files — no errors:

# module.yaml
name: stronghold
namespace: test
requirements:
  deckhouse: ">= 1.77"
  kubernetes: ">= 1.27"
  modules:
    mandatory-mod: ">= 1.0.0"
    optional-mod: ">= 1.0.0 !optional"

# package.yaml
name: stronghold
apiVersion: v2
requirements:
  deckhouse:
    constraint: ">= 1.77"
  kubernetes:
    constraint: ">= 1.27"
  modules:
    mandatory:
      - name: mandatory-mod
        constraint: ">= 1.0.0"
    conditional:
      - name: optional-mod
        constraint: ">= 1.0.0"

Inconsistent files — errors reported:

# module.yaml
name: stronghold
requirements:
  modules:
    some-module: ">= 1.0.0"         # mandatory here

# package.yaml
name: stronghold
requirements:
  modules:
    conditional:                     # but conditional here
      - name: some-module
        constraint: ">= 1.0.0"