Failing non-leader JM pod causes the deployment to be stuck in failing state

In case one of the JM replica pods cannot start but otherwise the job is healthy, the operator still cannot recognise the job in a running state.

This prevents for instance periodic savepoints to be taken or savepoint upgrades to be performed correctly.