Destroying resources with force should always succeed

[nicholasjackson]

Given a running environment that has partially failed and no Kubernetes cluster exists running down raises an error as the Kubernetes config can not be destroyed.

When down is called with --force it should never fail when destroying Kubernetes or Nomad config as ultimately the underlying clusters will be destroyed.

➜ jumppad down --force
Destroying resources  -- press ctrl c to cancel

INFO Destroying resources force=true
ERRO Unable to destroy stack
  error=
  │ error trying to call Destroy on provider: Error:
  │   unable to find dependent resource in module: '', error: 'Resource not found:
  │   resource.k8s_cluster.k3s'
  │ 
  │   /Users/nic/code/github.com/nicholasjackson/workshop-spring-vault/jumppad/k8s.hcl:33,1
  │ \x1b[2m     31 | \x1b[0m
  │ \x1b[2m     32 | # Configure the Vault Kubernetes service account\x1b[0m
  │ \x1b[2m     33 | resource "k8s_config" "vault_auth" {\x1b[0m
  │ \x1b[1m     34 |   disabled = !variable.install_vault\x1b[0m
  │ \x1b[2m     35 | \x1b[0m