refactor(vdev): migrate component example generation

[pront]

Motivation

Component documentation generation is currently split across vdev schema resolution, scripts/cue.sh, and a JavaScript example generator that passes data through website/data/docs.json. This makes the developer workflow harder to own, reuse, and optimize as one pipeline.

This follow-up consolidates the pipeline in vdev while preserving the already-merged example artifacts as a strict compatibility boundary.

Summary

• Move CUE docs-model generation from scripts/cue.sh build into cargo vdev build docs-json.
• Route make cue-build through the native vdev command.
• Avoid re-running CUE/example generation during check-generated-docs; its validator now consumes the artifacts the check already generated.
• Reuse component schema-resolution code where it preserves the final CUE model’s behavior.
• Keep website/generated/example-configs/ byte-for-byte unchanged throughout the refactor; those files are the parity fixtures.
• Measure and remove duplicate schema, CUE, and example-generation work only after confirming the current command graph.

The JavaScript component-example generator is intentionally unchanged in this first slice. It still
consumes the final CUE model, so this change establishes the native vdev boundary without altering
the generated examples or website output.

Developer impact

Contributors can now build the CUE docs model through vdev, using deterministic source discovery and
an explicit output path. The end state gives contributors one Rust developer tool for component-doc
and example generation, rather than coordinating shell and JavaScript entry points. It should also
eliminate website/data/docs.json as an internal generator-to-generator hand-off, while continuing
to produce it when Hugo needs it.

Vector configuration

Not applicable.

How did you test this PR?

• make check-markdown
• make check-clippy
• Compared cargo vdev build docs-json --output /tmp/vdev-component-docs.json byte-for-byte with scripts/cue.sh build output.
• Regenerated component examples through make -C website config-examples; website/generated/example-configs/ remained unchanged.
• make check-generated-docs (250 examples validated; 4 trace-only examples skipped; committed YAML fixtures unchanged).

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

• Related: Commit example configs - Add examples validation to CI #25943
• Follow-up to: docs(component docs): commit generated config examples #26002

[cose-datadog]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 7105763 | Docs | Datadog PR Page | Give us feedback!}