chore(api): integrate crd-enricher into CRD codegen

[prismagod]

Description

Integrate Deckhouse crd-enricher into the API CRD generation pipeline.
After controller-gen, enricher runs on the temporary CRD output (before files are copied to crds/), matching the flow in deckhouse#21220.

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

This enables +crd-enricher:raw:* and other markers in Go API types without editing generated CRD YAML by hand.

What is the expected result?

• cd api && task generate:crds completes successfully (Docker required for format:yaml)
• With no enricher markers, generated CRDs are unchanged after prettier

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: api
type: chore
summary: "Integrate crd-enricher into the API CRD codegen pipeline."