Generate project metadata documentation via automation

[kaylareopelle]

To disambiguate a code "owner" vs the reviewers, create an automated strategy to display a more specific code owner on a gem's Readme.

One option coudl be to follow the pattern established in otelcol-contrib where the Readme files have an auto-generated section:

Status
Stability	[beta]: traces, metrics, logs
Distributions	[contrib], [observiq], [splunk], [sumo]
Issues
Code Owners	@rnishtala-sumo

First discussed in: #879 (comment)

Here's an example PR demonstrating how this is done: open-telemetry/opentelemetry-collector-contrib#22800

It uses the mdatagen library, which isn't available in Ruby.

[dmathieu]

Note that while mdatagen is written in Go, and the documentation emphasizes the usage of //go:generate, it is actually only a binary that doesn't need a .go file to be executed.
It could be used within this repository rather easily, we'd just need to go install the binary in a pre-step.

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.