Use weaver for semantic convention codegen

[jsuereth]

I wasn't sure what you might want to change/fix about codegen when moving to weaver, so this attempts to keep the status quo as best as possible.

TODOs

• [x] Import markdown / notes -> javadoc filter to the Jinja weaver uses.
• [x] Finish supporting all types of template keys or throw an exception if an unsupported one shows up.
• [x] Remove previous jinja template
• [x] filter unwanted semconv groups in JQ expression in weaver config.
• [x] figure out what to do w/ K8S convention camel case.
• [x] Use type_mapping in weaver.yaml instead of macros.
• [x] Add stability: deprecated attributes back to incubating classes.

Possible Improvements thanks to weaver

• We could generate all the code (for incubating + stable) in the same weaver config, with the same shared set of templates. I kept it as-is for now so you can more easily compare what's happening.
• We can register name conversions for method/class/etc. for easier to understand case conversions.
• We can register acronymns, for consistent capitalization.

[jsuereth]

Update this, but we're now getting issues where weaver can't appropriately "javadoc-friendly" a comment, e.g.:

[ant:checkstyle] [ERROR] /home/joshuasuereth/src/open-telemetry/semantic-conventions-java/semconv/src/main/java/io/opentelemetry/semconv/ExceptionAttributes.java:26: <p> tag should be preceded with an empty line. [JavadocParagraph]

[jsuereth]

@jack-berg This is ready for review now. We have the javadoc/comment fixes in place for codegen.

I haven't consolidated down to calling weaver ONCE in gradle yet, but I can do that in a follow up PR.

[jsuereth]

Here are two minor suggestions:

1. Attributes are sorted by default, so most of the sort filters can be removed.

Fixed

2. The file name definition can be simplified, as detailed below.

I recommend using the new, simpler method to specify file names. For example, in IncubatingSemanticAttributes.java.j2, instead of:

{%- set my_file_name = ctx.root_namespace | pascal_case ~ "IncubatingAttributes.java" -%}
{{- template.set_file_name(my_file_name) -}}

you could define the file name directly in weaver.yaml within each template object like this:

templates:
  - template: "incubating_java/IncubatingSemanticAttributes.java.j2"
    filter: ...
    application_mode: ...
    file_name: ctx.root_namespace | pascal_case ~ "IncubatingAttributes.java"

FYI - the file_name is actually a JINJA template, not an expression, so it's:

templates:
  - template: "incubating_java/IncubatingSemanticAttributes.java.j2"
    filter: ...
    application_mode: ...
    file_name: "{{ctx.root_namespace | pascal_case}}IncubatingAttributes.java"

[jack-berg]

@jsuereth, @lmolkova, @lquerel, and @open-telemetry/java-approvers - I'll merge this tomorrow if there are no additional comments.