Backporting for 2.414.3

[krisstern]

Latest core version: jenkins-2.425

Fixed
-----

JENKINS-72067           Critical                Mon, 2 Oct 2023 06:06:22 +0000
        File system SCM uses more memory than expected with Jenkins 2.405 - 2.425
        regression
        https://issues.jenkins.io/browse/JENKINS-72067

JENKINS-72058           Major                   2.423
        Upgrade commons-compress to 1.24.0
        https://issues.jenkins.io/browse/JENKINS-72058

JENKINS-72016           Major                   2.425
        ProxyConfiguration.newHttpClientBuilder should maintain a thread pool
        https://issues.jenkins.io/browse/JENKINS-72016

JENKINS-71996           Minor                   Mon, 2 Oct 2023 06:00:27 +0000
        Backport security settings telemetry
        https://issues.jenkins.io/browse/JENKINS-71996

JENKINS-71890           Minor                   2.425
        model-links in Build History views no longer work (regression in 2.402)
        regression
        https://issues.jenkins.io/browse/JENKINS-71890

Notes

• 5 JIRA issues fixed as https://issues.jenkins.io/browse/JENKINS-61452?jql=labels%20%3D%202.414.3-fixed.
• No rejected issues yet for this backporting: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.414.3-rejected.

Desired reviewers

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