metric-schema includes the java version by default as a javaVersion tag

[carterkozak]

Before this PR

It was difficult to tie changes in performance or stability to a particular java release due to lack of data association.

After this PR

Note that I biased toward safety, excluding the new tag in cases where a javaVersion tag is already defined to avoid impacting existing dashboards, allowing upgrades to flow seamlessly.

==COMMIT_MSG==
metric-schema includes the java version by default as a javaVersion tag, for example javaVersion:17.0.3
==COMMIT_MSG==

Possible downsides?

Reported metrics are slightly larger, but the cardinality is unchanged.
System property load on class initialization isn't quite as nice as loading the java version once in a library and referencing it elsewhere, however this isn't going to be meaningful overall.

I'd considered adding this data in the reporting layer, however by adding it higher up in the process, it's clearer what data we produce.

[changelog-app]

Generate changelog in changelog/@unreleased

Type
See change types. Select one:

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

metric-schema includes the java version by default as a javaVersion tag, for example javaVersion:17.0.3

Check the box to generate changelog(s)

• Generate changelog entry

[svc-autorelease]

Released 0.17.0