[JENKINS-36193] Raise exception when trying to build a job that is disabled

[JENKINS-36476] Underprivileged users could not use the default value of a password parameter (#2454)

* [FIXED JENKINS-36476] Do not even send the default password in encrypted form; leave the text field blank, and apply the default upon submission.

* [JENKINS-36476] Use a special token, not the empty string, as the marker for the default value.

* [JENKINS-36592] Prevent NPE in BlockedBecauseOfBuildInProgress#getDescription() in the case of race condition

* [JENKINS-36592] - Address comments from @jglick

* [JENKINS-36592] - Fix wording. Attempt #2

* Fixed JENKINS-33201 [Java JSON exception with an empty parametrized
build.]

* FIXED JENKINS-33201. Changed to FormException instead of Failure

* That fix was never in a released version.

So it cannot have been reverted.

* Lowercase i for consistency

* Remove the concept of yanking dead executors.

* Another unnecessary call to doYank.

* [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.

* [JENKINS-27530] Noting #2439 & #2440.

* FIXED JENKINS-33201. Changed to FormException instead of Failure

* [FIXED JENKINS-33201 .FormException is thrown if parameterDefinitions are not available .

* Changing one more Tab to Space

* Moved checkForEmptyParameters to Job class

* [JENKINS-36593] - ItemCategory#MIN_TOSHOW should be restricted

* [JENKINS-36593] - Add Javadoc

[FIXED JENKINS-36594] - CauseOfInterruption.UserInterruption#getUser() should not create new users (#2450)

* CauseOfInterruption.UserInterruption#getUser() should not create new users if the user gets deleted before the cause printing call

* [JENKINS-36594] - Print raw username if we cannot create MasterHyperlinkNote

* [JENKINS-36387] Catch exception when scm retry count field is empty.

* Add test for JENKINS-36387

* [JENKINS-36387] Move test in correct place

* [JENKINS-36387] Reproduce actuall behaviour

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