Backporting for LTS 2.516.1 (part 1)

[MarkEWaite]

Backporting for LTS 2.516.1 (part 1)

See

• JENKINS-75818 - add event listener to trigger compute
  • [JENKINS-75818] add event listener to trigger compute #10772
• JENKINS-75834 - make sure only one instance of the dropdown is visible
  • [JENKINS-75834] make sure only one instance of the dropdown is visible #10786
• JENKINS-75853 - Remove active look of hamburger button
  • [JENKINS-75853] - Remove active look of hamburger button #10804
• JENKINS-758532 - actions in the hamburger menu with badges do not render correctly
  • [JENKINS-75832] Support actions with Badges in the Hamburger Menu #10791
• JENKINS-758549 - script console can be used with sidepanel
  • [JENKINS-75849] Makes scriptConsole layout configurable #10800

JENKINS-75818           Minor                   2.517
        In case custom plugins add items to the breadcrumb the initial rendering is not collapsing the path
        https://issues.jenkins.io/browse/JENKINS-75818

JENKINS-75834           Major                   2.518
        Dropdown can produce multiples dropdowns visible
        https://issues.jenkins.io/browse/JENKINS-75834

JENKINS-75853           Minor                   2.518
        Secondary actions in header look focused
        https://issues.jenkins.io/browse/JENKINS-75853

JENKINS-75832           Major                   2.518
        actions in the hamburger menu with badges do not render correctly
        https://issues.jenkins.io/browse/JENKINS-75832

JENKINS-75849           Major                   2.518
        script console can be used with sidepanel
        https://issues.jenkins.io/browse/JENKINS-75849

Testing done

Confirmed each of the individual commits in the pull request matches the original commit on the master branch.

Ran a quick-build and confirmed that the active look of hamburger button was resolved.

Proposed changelog entries

N/A

Proposed changelog category

/label into-lts

Proposed upgrade guidelines

N/A

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

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

[MarkEWaite]

The failing test inQueueTaskLookupByAPI is reported as flaky by launchable

[jglick]

#10786 (comment)