docs(specs): Publish spec compliance matrix

[lehmannro]

• 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.¹

---

This will publish the Compliance of Implementations with Specification matrix, currently only on Github, under https://opentelemetry.io/docs/languages/spec-compliance-matrix (titled Spec compliance.)

Footnotes

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

[lehmannro]

I realize some of the links are still broken; could I get some indication if the approach is sane in general, then I'll happily tweak adjust-pages.pl some more.

[svrnm]

Preview: https://deploy-preview-9358--opentelemetry.netlify.app/docs/languages/spec-compliance-matrix/

Interesting idea & solution, @lehmannro , we need to check a few things here, if this is maintanable long term.

@open-telemetry/spec-sponsors PTAL!

[thompson-tomo]

Would it make more sense for this to reside alongside the spec within the spec branch of the navigation.

It might be useful to see if we could also generate 1 page per language and have that mounted under the appropriate language. That way if someone is looking at the .net docs they can easily see what features have been implemented.

[lehmannro]

I went and fixed up all links through adjust-pages.pl now. I believe the remaining check-links failures are false positives (they're the Edit this page and View page source links.)

As for where in the navigation this lives, I don't feel strongly. To me, Languages makes most sense because I'd probably use this page when I'm looking at a particular language / across languages, rather than into the specification only. YMMV.

Splitting up sounds like a more involved project because we'd need to fetch the individual YAML files and generate our own tables, much like the current opentelemetry-specification script already does.
I can see value in doing both, so maybe we get this exported now and then, if we still have the appetite (for both the effort and the additional complexity) add per-language tables later?