Dataproc module cleanup & fixes

[wiktorn]

• added end-to-end tests for dataproc module, regrettably - GCE example proved to be flaky in tests - so it is disabled (the depends_on is not always enough for the cluster creation to complete successfully, sometimes manual retry is required)
• included in the examples necessary components (firewall rules, permissions)
• added fixture for GKE cluster
• removed unused variable service_account - properly managing service account within module is left as excessive for future reader / self
• removed variable prefix as it doesn't make much sense in this context
• removed output variables as due to bugs in the terraform provider they are not returned and result in terraform plan errors after apply

Error on GCE dataproc cluster apply:

│ Error: Error waiting for creating Dataproc cluster: Error code 13, message: 
│ Failed to initialize node my-cluster-m: Failed to create event log dir with 403 HTTP response code and 22 exit code.  Please check if Service Account has permission to create directory in dataproc-temp-*** GCS bucket. See output in: gs://***/google-cloud-dataproc-metainfo/d12144b5-b1b5-4b60-8cea-26ac5faa941f/my-cluster-m/dataproc-startup-script_output
│ 
│   with module.processing-dp-cluster.google_dataproc_cluster.cluster,
│   on ***/cloud-foundation-fabric/modules/dataproc/main.tf line 19, in resource "google_dataproc_cluster" "cluster":
│   19: resource "google_dataproc_cluster" "cluster" {

Second apply (recreates cluster) works without error.

E2E Run

See: #2127

---

Checklist

I applicable, I acknowledge that I have:

• Read the contributing guide
• Ran terraform fmt on all modified files
• Regenerated the relevant README.md files using tools/tfdoc.py
• Made sure all relevant tests pass

[ludoo]

Great work Wiktor :)