Backporting 2.479.2 LTS - Part 2

[krisstern]

Latest core version: jenkins-2.484

Fixed
-----

JENKINS-74852           Minor                   TBD
        Update script-security to 1368.vb_b_402e3547e7
        https://issues.jenkins.io/browse/JENKINS-74852

JENKINS-74826           Minor                   2.485 (upcoming)
        Backport the xstream 1.4.21 upgrade to Jenkins 2.479.2
        https://issues.jenkins.io/browse/JENKINS-74826

JENKINS-74814           Minor                   <a href="https://www.jenkins.io/changelog/2.485/">https://www.jenkins.io/changelog/2.485/</a>
        java.lang.UnsupportedOperationException: This stack walker does not have RETAIN_CLASS_REFERENCE access
        https://issues.jenkins.io/browse/JENKINS-74814

JENKINS-74795           Minor                   <a href="https://www.jenkins.io/changelog/2.485/">https://www.jenkins.io/changelog/2.485/</a>
        Job created via REST API attaches to default view (regression in 2.475)
        regression
        https://issues.jenkins.io/browse/JENKINS-74795

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

@timja @daniel-beck @MarkEWaite @basil

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

[daniel-beck]

Everything except script-security is already in #9956

[basil]

Thanks!