Backporting for LTS 2.516.2 - JENKINS-75637

[MarkEWaite]

Backporting for LTS 2.516.2 - JENKINS-75637

Latest core version: jenkins-2.522

Fixed
-----

JENKINS-75637           Major                   2.520
        System configuration no longer has breadcrumb navigation (regression in 2.507)
        regression
        https://issues.jenkins.io/browse/JENKINS-75637

Cherry picked individual commits from pull request:

• [JENKINS-75637] Fix System configuration page no longer having breadcrumb navigation  #10715

Testing done

Interactive testing to confirm the system menu has breadcrumbs.

Confirmed with a diff that the modified source files match with the source files on the master branch when the pull request was merged to master.

/label into-lts

Submitter checklist

• The Jira 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.
• 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

@timja @basil

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, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).