Update helmfile defaults for faster helm deployments.

[willgraf]

All of our helmfiles were using the same default values, specifically timeout: 600. This PR updates those defaults by:

• Adding a specific timeout to each release. (Fixes #267)
  • 600 was kept for long-running deployments (redis, openvpn, prometheus-operator)
  • 180 for cluster-issuers (inspired by cloudposse)
  • 300 for everything else (this can always be changed later on)
• force: true was removed for all helm deployments, which was causing some issues with helm3.
• atomic: true and cleanupOnFail: true were added to all releases. Having helm do the cleanup lets us clean up some of our deployment wrapper script.
• Comments were generally improved, and links were added for all helmfile references.
• Update helmfile deployment script to log all helmfile failures and instructions for re-installing. No longer calls helm delete as each helmfile has atomic and cleanupOnFailure enabled. (Fixes #349)

[willgraf]

Please see below for an example of the helmfile failure output/warnings.

[MekWarrior]

I like alot of what is there but I do have a couple concerns. First, we need to make sure docs are clear on where to run the helmfile -l name=... command. Second, the message seems contradictory. On the one hand we say "Not all .... successfully deployed" but at the end we say "...created successfully." This could cause confusion and the early message may be disregarded - and subsequently lost to the logs.