Backporting for 2.479.1

[MarkEWaite]

Backporting for 2.479.1

Latest core version: Jenkins 2.479

Candidates included

JENKINS-73867           Minor                   2.480
        Backport the override of outdated managed dependency on asm
        https://issues.jenkins.io/browse/JENKINS-73867

JENKINS-73838           Minor                   2.480
        Compatibility for Jenkins#doSafeRestart(StaplerRequest, String)
        regression
        https://issues.jenkins.io/browse/JENKINS-73838

JENKINS-73801           Minor                   2.480
        Nested Views plugin overrides View#doConfigDotXml(StaplerRequest)
        regression
        https://issues.jenkins.io/browse/JENKINS-73801

JENKINS-73760           Major                   2.480
        Updates fail due to invalid JSON from HTTP updates.jenkins.io (HTTPS is ok)
        https://issues.jenkins.io/browse/JENKINS-73760

JENKINS-73437           Minor                   2.480
        the build history widget displaying a very long http link, it looks a bit bad
        https://issues.jenkins.io/browse/JENKINS-73437

Backported issues include:

• JENKINS-73437 Backport the override of outdated managed dependency on asm
• JENKINS-73760 Compatibility for Jenkins#doSafeRestart
• JENKINS-73801 Nested Views plugin overrides View#doConfigDotXml
• JENKINS-73838 Switch update center to https://updates.jenkins.io for older installs
• JENKINS-73867 Wrap long build description text in the build history widget

Testing done

• JENKINS-73867 Wrap long build description text in the build history widget.
  Confirmed that long build description text is wrapped for freestyle and Pipeline jobs

Other backports rely on automated tests to confirm.

Proposed changelog entries

N/A

Proposed upgrade guidelines

N/A

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

N/A

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

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!