[JENKINS-36629] Optimization for recent build stability calculation

Use LoggerRule

The test found out that RunMap's subMap implementation only returns loaded builds, so we needed to introduce a method to test if there was a specific run on the disk. For the weather reports we do not care if the record on the disk fails to load

Optimization for recent build stability calculation that should at most load two builds into memory for the recently stable case. In the non-recently stable case we just pre-load the most recently stable one and skip loading any intermediary successful ones

* [JENKINS-35570] List of computer's names extracted to Util

[JENKINS-35423] CLI commands quiet-down/cancel-quiet-down extracted from core to CLI

[FIXED JENKINS-36494] Switch to a try with resources form of impersonation

* JENKINS-34668 - setup wizard installing panel unusable on small screens

[JENKINS-27530] nextBuildNumber snafu after reload

Remove the concept of yanking dead executors

[JENKINS-36494] Clarify that the previousContext is never `null` per JavaDoc for `SecurityContextHolder.getContext()`

So it cannot have been reverted.

[FIXED JENKINS-27530] Jenkins.reload must also reload the Queue to ensure that every Queue.Item.task corresponds to a live Job, lest nextBuildNumber be bogus.

@oleg-nenashev created a BasicCredentialsProvider for SetupWizardTest but seems to have never used it.

[JENKINS-25416][JENKINS-28790] - Fix the parametersReferencedFromPropertiesShouldRetainBackslashes() test, which relies on the legacy behavior (#2435)

The test fails after https://github.com/jenkinsci/jenkins/pull/1976/commits/84ee34f2df620f1280022f1678b81e5c27dfc330