Fix issues when startup timeout is hit

[georgew5656]

Description

Fixes a bug in the K8s Task Runner when k8sjobLaunchTimeout is hit during launchPeonJobAndWaitForStart in KubernetesPeonLifecycle.run without the task pod successfully coming up, e.g. when there is no available node.

Currently if a task pod fails to come up in time, the overlord marks the task as failed and logs the timeout error message, but doesn't actually cleanup the job. Eventually the cleanupExecutor will cleanup the job, but it's possible for the job to fail to come up in k8sjobLaunchTimeout, then succeed afterwards and actually run even though the overlord has marked it as failed.

Release note

Fix a bug with the K8s overlord extension

Key changed/added classes in this PR

Update KubernetesPeonsLifecycle to cleanup jobs it has tried to start and that haven't come up.

This PR has:

• [ X] been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• [X ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• [X ] been tested in a test Druid cluster.

[suneet-s]

Nice catch!