JENKINS-54662 JCasC support for usage statistics

[timja]

See JENKINS-54662.

Example configuration:

jenkins:
  noUsageStatistics: true

Proposed changelog entries

• Entry 1: JENKINS-54662, configuration-as-code plugin support for disabling usage statistics
• ...

Proposed upgrade guidelines

N/A

Submitter checklist

• JIRA issue is well described
• Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
  • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
• Appropriate autotests or explanation to why this change has no tests
• For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

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

• There are at least 2 approvals for the pull request and no outstanding requests for change
• Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
• Changelog entries in the PR title and/or Proposed changelog entries are correct
• Proper changelog labels are set so that the changelog can be generated automatically
• If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
• If it would make sense to backport the change to LTS, a JIRA issue should exist and be labeled as lts-candidate

[jetersen]

Seems reasonable

[oleg-nenashev]

The code itself looks good to me. Added some suggestions for Javadoc so that two methods can be distinguished easily.

[oleg-nenashev]

It was introduced in 2011 or earlier, so it is not a big deal. All reasonable versions will be compatible 70c1065

[timja]

This is ready-for-merge, let's merge it in 24 hours if no negative feedback