Weaver-ify metadata

The scope and nature of this issue is likely to evolve over time, but the primary goal is to take the work done so far to populate and generate metadata for instrumentation modules, and use it to bootstrap weaver compliant yaml files per instrumentation.

Ideas as of now:

• Evaluate the current metadata structure and data, and start mapping it into the equivalent weaver concepts. This means renaming some of the metadata attributes in the existing yaml files and instrumentation-list.yaml catalog (telemetry -> signals etc).
• Instead of only storing the signal information in the resulting instrumentation-list.yaml, we'll update our existing automation to populate/manage "signal" weaver files per module

It's not clear to me yet whether we will continue needing to manage a separate metadata file of some sort that contains things not currently supported in the weaver schema, but hopefully we can consolidate things so that it doesn't get too complicated to maintain.

End goal:

• Weaver compliant metadata files per instrumentation module that can be used to generate readme's in each directory, or referenced/used by other tools
• Weaver live check is used to evaluate and identify which modules emit only stable instrumentation by default (#14351)