fix(health): OutOfService is a Down health state (spinnaker#3638)

* refactor(health): use clouddriver's HealthState model

Behavior should be unchanged

* fix(health): OutOfService is a Down health state

When we're waiting for up instances, OutOfService was considered neither Up nor Down, which means that as long as some other health was Up, having one OutOfService would not keep the task waiting.

With this change, we consider OutOfService a Down status, which means that someAreUpAndNoneAreDown will return false, which will keep the task waiting.

* fix(test): fix WaitForUpInstanceHealthTaskSpec

* chore(javadoc): turn comment into javadoc in HealthState

fix(bake): Bake respect regions (spinnaker#3627) (spinnaker#3656)

Co-Authored-By: Mark Vulfson <[email protected]>
(cherry picked from commit 86ca311)

Co-authored-by: Edgar Garcia <[email protected]>

fix(core): revert configurable timeouts (bp spinnaker#3644) (spinnake…

…r#3646)

fix(build): Try 6 remote repository deploy attempts before failing (s…

…pinnaker#3645)

fix(build): 2 minute Gradle HTTP client socket and connection timeout (…

…spinnaker#3643)

chore(dependencies): Autobump spinnakerGradleVersion (spinnaker#3639)

Co-authored-by: root <root@3ba87f91c30c>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

chore(dependencies): Autobump spinnakerGradleVersion (spinnaker#3639)

Co-authored-by: root <root@3ba87f91c30c>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

fix(kubernetes): Fix artifact binding in patch manifest stage (spinna…

…ker#3605) (spinnaker#3606)

The patch manifest stage was incorrectly setting allArtifacts to
just the required artifacts, which was breaking artifact resolution
in clouddriver. Set this to all of the artifacts (both required and
optional).

(cherry picked from commit c550856)

Co-authored-by: Eric Zimanyi <[email protected]>

fix(kubernetes): correctly write Patch Manifest patchBody (spinnaker#…

…3602) (spinnaker#3603)

Prior to [this refactor](spinnaker#3402), PatchManifestTask read patchBody
directly from the ManifestEvaluator's result. Now, we are attempting to read it off the stage's context,
but we deserialized the context with the same model, PatchManifestContext, that we used to deserialize the
initial stage inputs, which tries to read manifests from patchBody (at this point, we should be reading
manifests from the manifests key instead). This is intended to be a cherry-pickable fix, but a better
more invasive fix would define different models for the inputs and outputs of each task and assert that
the context had required values before beginning the task.

Co-authored-by: Maggie Neterval <[email protected]>

chore(bakeManifest): Update BakeManifest error when missing expectedA…

…rtifact (spinnaker#3593) (spinnaker#3596)

(cherry picked from commit db3cc93)

Co-authored-by: Justin Lee <[email protected]>