Backporting 2.462.3 LTS

[krisstern]

Latest core version: jenkins-2.476

Fixed
-----

JENKINS-73743           Minor                   Mon, 16 Sep 2024 11:20:52 +0000
        Backport Winstone 6.22 and Jetty 10.0.24 into 2.462.3
        https://issues.jenkins.io/browse/JENKINS-73743

JENKINS-73692           Major                   <a href="https://github.com/jenkinsci/jenkins/releases/tag/2.475">https://github.com/jenkinsci/jenkins/releases/tag/2.475</a>
        BackgroundGlobalBuildDiscarder creates lots of log output
        https://issues.jenkins.io/browse/JENKINS-73692

JENKINS-73668           Minor                   <a href="https://www.jenkins.io/changelog/2.474/">https://www.jenkins.io/changelog/2.474/</a>
        Uprade Plugins: Action list too small
        regression
        https://issues.jenkins.io/browse/JENKINS-73668

JENKINS-73422           Minor                   <a href="https://github.com/jenkinsci/jenkins/releases/tag/2.475">https://github.com/jenkinsci/jenkins/releases/tag/2.475</a>
        JENKINS-72636 breaks scripted downloads
        https://issues.jenkins.io/browse/JENKINS-73422

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

@MarkEWaite @daniel-beck @timja @basil @NotMyFault @mwinter69 @jglick

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).

[krisstern]

JENKINS-73743 to be included in #9698