[maven-release-plugin]prepare release v4.6.2
[maven-release-plugin]prepare for next development iteration
Fixed SocketTimeoutException handling for job alert. Ref T50541
Catch all exception during alert scan. Added alert to healthcheck. Ref T50588
Oops remove test code. Ref T50588
[maven-release-plugin]prepare release v4.6.3
[maven-release-plugin]prepare for next development iteration
Json ignore a previously removed JobAlert property to prevent deser error of old alerts. Ref T50588
three query file ref replacement fixes T50660

1. a typo caused the replacement file ref to come from the old list
   rather than the new/good list. (reference -> newReference; The
   old variable named reference was also changed to oldReference to
   help with future clarity).
2. most places used HashMultimaps, which do not allow duplicates.
   However, some of the replacement logic used ImmutableMultimaps,
   and those do (undesirably) allow duplicates unless the more
   specific ImmutableSetMultimap is used. This could allow the number
   of file reference entries to grow rather large in some edge cases.
3. updating the file ref cache with the new list of entries merged the
   new/good list with the old entries. This is fine for the basic case
   because the replacement ref is taken directly from the new/good
   list. However, if there are two or more bad options, then this logic
   could cause them to continuously alternate between each other, as
   the new/good list only prunes one bad entry at a time, and the merge
   would revive the bad ones as choices for the next call.
Fixed healthcheck js code. Ref T50588
Only check distinct set of jobs per alert. Ref T50588

Some alerts are set up with job ids and aliases that resolve to the same
job, resulting in checking the alert against a list containing duplicate
jobs. Aside from being wasteful, that causes duplicate key exception 
when building error message map because job ids are used as the key.
[maven-release-plugin]prepare release v4.6.4
[maven-release-plugin]prepare for next development iteration
work-arounds for interrupt handling in muxy/bdb

these hacks should eventually be replaced when I decide on how
to refactor (a)sync start/stop/error reporting between various
threaded sub-components
fix NPE in rebalancing; extract HostManager

The NPE could occur when rebalancing a job that has many disabled
minions holding tasks for it. This caused the job to error and
enter a weird state besides.

HostManager basically just handles the lowest level operations
surrounding the ConcurrentMap of HostStates. It manages to replace
overkill-Spawn references in a couple places, and is another step
in our goal of breaking down Spawn responsibilities to eg. enable
us to stop passing "this" everywhere and clarify inter-dependencies.
add docs for spawn.conf

the scope is somewhat broader than it needs to be for just the one
file, but it addresses some of the more common confusions.
stream directories during file stats

directories with enormous numbers of files are bad to enumerate
as a giant array
Fix typo in generated hydra user reference.
Only allow a disabled job to be enabled if it’s idle. Ref T50807
Better job enable/disable API and UI code. Ref T50807