Dataproc autogen bucket changes (hashicorp#1171)

* add extra wait for storage bucket object deletion

* make timeout for object deletion 5 minutes, make it succeed 3 times

* delete the cluster before deleting the bucket

* deprecate delete_autogen_bucket

* improve deprecation message

Author: danawillow

docs/r/dataproc_cluster.html.markdown

@@ -32,7 +32,6 @@ resource "google_dataproc_cluster" "mycluster" {
     }
 
     cluster_config {
-        delete_autogen_bucket = true
         staging_bucket        = "dataproc-staging-bucket"
 
         master_config {
@@ -105,8 +104,6 @@ The **cluster_config** block supports:
 
 ```hcl
     cluster_config {
-        delete_autogen_bucket = true
-
         gce_cluster_config        { ... }
         master_config             { ... }
         worker_config             { ... }
@@ -126,10 +123,11 @@ The **cluster_config** block supports:
    with other clusters in the same region/zone also choosing to use the auto generation
    option.
 
-* `delete_autogen_bucket` (Optional) If this is set to true, upon destroying the cluster,
+* `delete_autogen_bucket` (Optional, Deprecated) If this is set to true, upon destroying the cluster,
    if no explicit `staging_bucket` was specified (i.e. an auto generated bucket was relied
    upon) then this auto generated bucket will also be deleted as part of the cluster destroy.
-   By default this is set to false.
+   By default this is set to false. This value is deprecated: autogenerated buckets are shared by
+   all clusters in the same region, so deleting the bucket could adversely harm other dataproc clusters.
 
 * `gce_cluster_config` (Optional) Common config settings for resources of Google Compute Engine cluster
    instances, applicable to all instances in the cluster. Structure defined below.