Prototype 2.541.1 backport 1

[MarkEWaite]

Prototype of 2.541.1 based on current (wrong) stable-2.541

Draft - do not merge. Needs much more analysis to confirm it is correct and complete

Backports the following issues and matching pull requests:

• Add telemetry for CSP enforcement #23900
  • Add telemetry for Content Security Policy #23901
• Allow disabling CSP headers entirely to work around problems in unusual environments #23914
  • Allow entirely disabling CSP headers #23915
• Increase default HTTP response header size limit #25900
  • Update Winstone and Jetty #23909
  • Update Winstone to 8.1026.v31def012a_f48, add test confirming the CSP response header can be >30KB #25901
• Form is larger than max length 200000 #25958
  • Update dependency org.jenkins-ci:winstone to v8.1029.vd3071f6b_5988 #25968
• Console copy button on freestyle job does not copy to clipboard #25976
  • Re-add out id to Console Output #25953
• Cloud sidepanel uses relative urls causing 404 in actions attached to the cloud #26002
  • Use rootURL in Cloud sidepanel so links in actions work properly #26004
• Collect telemetry for Java properties #26040
  • Collect telemetry for Java properties #26038

Testing done

None. Using ci.jenkins.io to build it so that I can do more checks later.

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. The official pull request is available as:

• Backport 2.541.1 #26070