Dynamic declarative configuration spec types page

[jaydeluca]

• I have read and followed the Contributing docs, especially the "First-time contributing?" section.
• This PR has content that I did not fully write myself.
  • I used AI and I have read and followed the Generative AI Contribution Policy.
• I have the experience and knowledge necessary to understand, review, and validate all content in this PR.¹

---

Part of #9521

Builds on top of #9654 and #9842

This introduces the dynamic types page within the spec/configuration directory. One note is that @chalin and I had discussed ensuring there was also an LLM friendly markdown version of the page, and this PR does not handle that. I have accounted for that in my plans for followup PRs.

I have plans for integrating code snippets in a followup as well

Deployment preview: https://deploy-preview-9850--opentelemetry.netlify.app/docs/specs/otel/configuration/types/

cc @jack-berg

Footnotes

1. Yes, I can answer maintainer questions about the content of this PR, without using AI. ↩

[jaydeluca]

there's something odd going on with the links, im working on figuring it out

[jack-berg]

Ah so good. 👏 👏

@open-telemetry/configuration-approvers definitely go check this out.

There's a few missing features from schema-docs.md which I still find useful, but not necessary to start. Let's take OtlpHttpExporter as an example:

• There's a language support status table that shows the support of each property in each language at a glance.
• There's a Usages section, that provides links to the other places in the schema where the type is used, and provides a very useful "infinite linking" feature. To help folks get started, the Overview section links to the OpenTelemetryConfiguration root type. <-- That's the common thing you want to do. Start at the root and click down through the property tree. The type column of your tables could also participate in this infinite linking.
• There's a snippets section, where each reference snippet is included in a collapsible section. Lots of useful little tidbits in these snippets, including explanatory comments.
• There's a JSON schema source section, that defines the raw JSON schema definition for the type. This is helpful because sometimes the rendering isn't perfectly expressive of the underlying type definition. Sometimes you just gotta go to the source code, and this facilitates that.