[WIP] Test Spring 7 and other PRs

[MarkEWaite]

[WIP] Test Spring 7 and other PRs

A fast incremental build to allow plugin BOM and acceptance test harness testing of pull requests:

• Update dependency org.springframework.security:spring-security-bom to v7 #11304
• Update dependency org.springframework:spring-framework-bom to v7 #11292

Also includes pull requests:

• Describe BASE+EXTRA syntax in help for global environment variables #26447
• AccessDeniedException3 was unserializable #26446
• Simplifying implementation of DirectoryBrowserSupport #26443
• Update dependency sass to v1.98.0 #26440
• Update dependency mini-css-extract-plugin to v2.10.1 #26439
• Remove maximum width of sections #26435
• Update jenkins/ath Docker tag to v6595 #26434
• Update dependency css-minimizer-webpack-plugin to v8 #26429
• Update dependency babel-loader to v10.1.1 #26428
• Update dependency eslint to v10.0.3 #26427
• Added Turkish translation to setup wizard. #26426
• Update release-drafter/release-drafter action to v6.4.0 #26421
• Update stapler.version to v2078 (major) #26414
• Update dependency postcss to v8.5.8 #26411
• Update Winstone and Jetty #26403

Testing done

• Confirmed that mvn -am -pl war,bom -Pquick-build clean install ran as expected
• Ran a few simple interactive tests using a Linux agent and a Linux controller with a Pipeline job

Screenshots (UI changes only)

Before

After

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]

Incremental build has been created. Closing