Support new upgrade-replace logic from Helm 3.3

[tkrullmann]

Starting with Helm 3.3, helm upgrade replaces a previous deployment if the history consists entirely of failed deployments. This means that now installation or upgrade can now always be performed with helm upgrade --install, regardless of the previous state of the deployment.

Currently the HelmInstallOrUpgrade task does a helm ls first to check if the deployment has previously failed, and then decides whether to use helm upgrade --install or helm install --replace. For Helm 3.3 we could skip this check because helm upgrade --install would now always behave like this.

However, we also want to keep supporting Helm versions < 3.3, so this would mean we have to read the version using helm version first. But helm version does not make a network call, so it should still be an improvement over helm ls.