Create incremental build for BOM and ATH test

[MarkEWaite]

Create incremental build for BOM and ATH testing

Do not merge

Includes pull requests that are currently marked as "Ready for merge":

• Bump minimum supported remoting version #26034
• Fix race condition during initial admin account creation #26036
• Collect telemetry for Java properties #26038
• Update dependency com.puppycrawl.tools:checkstyle to v12.3.1 #26041
• Update dependency io.jenkins.plugins:jakarta-xml-bind-api to v4.0.6-12.vb_1833c1231d3 #26042
• Update dependency io.jenkins.plugins:jaxb to v2.3.9-143.v5979df3304e6 #26043
• Update dependency io.jenkins.plugins:checks-api to v402 #26044
• Update dependency org.jenkins-ci.plugins:credentials to v1460 #26046
• Update dependency io.jenkins.lib:support-log-formatter to v121 - autoclosed #26048

The incremental failed my local testing when it had the "Require Java 21" pull requests. In order to test the listed pull requests, I reverted pull requests:

• Require Java 21 or newer #26018
• Update stapler.version to v2065 (major) #26049

Testing done

Confirmed that a local build compiles and passes a small test. I want the additional safety to check an incremental in the plugin BOM and the acceptance test harness.

Proposed changelog entries

• N/A

Proposed changelog category

/label skip-changelog

Proposed upgrade guidelines

N/A

Submitter checklist

• The issue, if it exists, is well-described.
• 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.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• UI changes do not introduce regressions when enforcing the current default rules of Content Security Policy Plugin. In particular, 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).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

N/A

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

Maintainer checklist

• There are at least two (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 is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• 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).
• If it would make sense to backport the change to LTS, be a Bug or Improvement, and either the issue or pull request must be labeled as lts-candidate to be considered.

[MarkEWaite]

Closing because the BOM tests all passed with the revert of "require Java 21" and the acceptance test harness passes except for the one known flaky test.