Add telemetry for basic Java system properties

[daniel-beck]

This could be useful to collect. There is some overlap with the general usage stats (so not all of this will be new), and it doesn't get agent JVM information, but still. I think this tells us more about OS and JVM than what we currently know.

Testing done

No dedicated autotest due to the similarity with other similar telemetry implementations.

ExtensionList.lookupSingleton(jenkins.telemetry.impl.JavaSystemProperties).createContent()

Output:

Result: {"file.encoding":"UTF-8","file.separator":"/","java.vm.name":"OpenJDK 64-Bit Server VM","java.vm.vendor":"Eclipse Adoptium","java.vm.version":"11.0.15+10","os.arch":"aarch64","os.name":"Mac OS X","os.version":"13.6.1","user.language":"en","components":{"bouncycastle-api":"2.29","caffeine-api":"3.1.8-133.v17b_1ff2e0599","commons-lang3-api":"3.13.0-62.v7d18e55f51e2","commons-text-api":"1.10.0-78.v3e7b_ea_d5a_fe1","ionicons-api":"56.v1b_1c8c49374e","jackson2-api":"2.15.2-350.v0c2f3f8fc595","javax-activation-api":"1.2.0-6","jaxb":"2.3.9-1","jenkins-core":"2.436-SNAPSHOT","matrix-auth":"3.2.1","scm-api":"676.v886669a_199a_a_","script-security":"1275.v23895f409fb_d","snakeyaml-api":"2.2-111.vc6598e30cc65","structs":"325.vcb_307d2a_2782"}}

On Configure System, the help shows as expected:

Ran ExtensionList.lookupSingleton(jenkins.telemetry.Telemetry$TelemetryReporter).run() and confirmed it shows up in Uplink.

Added a test property to the list to ensure it renders correctly:

Result: {"file.encoding":"UTF-8","file.separator":"/","java.vm.name":"OpenJDK 64-Bit Server VM","java.vm.vendor":"Eclipse Adoptium","java.vm.version":"11.0.15+10","os.arch":"aarch64","os.name":"Mac OS X","os.version":"13.6.1","test":"(undefined)","user.language":"en","components":{"bouncycastle-api":"2.29","caffeine-api":"3.1.8-133.v17b_1ff2e0599","commons-lang3-api":"3.13.0-62.v7d18e55f51e2","commons-text-api":"1.10.0-78.v3e7b_ea_d5a_fe1","ionicons-api":"56.v1b_1c8c49374e","jackson2-api":"2.15.2-350.v0c2f3f8fc595","javax-activation-api":"1.2.0-6","jaxb":"2.3.9-1","jenkins-core":"2.436-SNAPSHOT","matrix-auth":"3.2.1","scm-api":"676.v886669a_199a_a_","script-security":"1275.v23895f409fb_d","snakeyaml-api":"2.2-111.vc6598e30cc65","structs":"325.vcb_307d2a_2782"}}

Why even test for null? While I expect it to always exist, https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/System.html#getProperties() doesn't list file.encoding as part of the default set, so I added this to be safe.

Proposed changelog entries

• Add telemetry for basic Java system properties describing the environment

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[daniel-beck]

Required to be able to access it (the current Telemetry implementation) in description.jelly.

[timja]

LGTM

[NotMyFault]

/label ready-for-merge

---

This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback.
Please see the merge process documentation for more information about the merge process.
Thanks!