Handle GKE AUTH intermittent errors

[mirestrepo]

The way this module is structured is causing intermittent errors on terraform refresh. As a work around we are sometimes turning the refresh=false

There are several issues around:

• This issue points tor parallelism but that's not the case. There are few linking issues in there that are useful, including this PR that still seems to be open
• This short blog post links to two useful resources. One for the Kubernetes provider docs which includes the following warning

When using interpolation to pass credentials to the Kubernetes provider from other resources, these resources SHOULD NOT be created in the same Terraform module where Kubernetes provider resources are also used. This will lead to intermittent and unpredictable errors which are hard to debug and diagnose. The root issue lies with the order in which Terraform itself evaluates the provider blocks vs. actual resources. Please refer to this section of Terraform docs for further explanation.

The section mentioned on the terraform docs, likely is the most informative:

The body of the block (between { and }) contains configuration arguments for the provider. Most arguments in this section are defined by the provider itself; in this example both project and region are specific to the google provider.

You can use expressions in the values of these configuration arguments, but can only reference values that are known before the configuration is applied. This means you can safely reference input variables, but not attributes exported by resources (with an exception for resource arguments that are specified directly in the configuration).

Two ideas here. Either move the auth into the jujube_module where the provider lives or we separated jupyterhub into two modules. One for it's infrastructure and one for helm part so they live in two different applies