docs(component docs): commit generated config examples

[pront]

Summary

Component examples are currently generated into ignored website/data/docs.json. That makes config changes unavailable for review and prevents CI from detecting drift or validating the generated configurations. These examples are the first section readers encounter in component documentation, so keeping them valid is essential to making the docs trustworthy. This PR commits the YAML artifacts and makes them an independently validated CI input.

• Generate 254 minimal and advanced YAML examples under website/generated/example-configs/.
• Keep Hugo's multi-format examples populated from the same generation pass.
• Detect stale generated examples and validate the committed YAML in the generated-docs CI job.
• Run the job when its generator, validator, CUE, Makefile, or generated-artifact inputs change.
• Reuse the target/debug/vector binary already built for schema generation. The job's shared Cargo/target cache avoids a second full Vector build for validation.

Vector configuration

Not applicable; this changes generated component example artifacts and their validation.

How did you test this PR?

• make generate-example-configs
• make -C website validate-config-examples — 250 examples validated; 4 trace-only examples skipped; completed in about 18 seconds.
• make check-fmt
• git diff --check

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

• Closes Commit example configs - Add examples validation to CI #25943

[cose-datadog]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 61fcab1f40

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".