samples/guestbook: GCP section fails on terraform apply

[enocom]

Terraform fails to provision GCP resources with the following errors:

Error: Error applying plan:

4 error(s) occurred:

* google_project_service.container: 1 error(s) occurred:

* google_project_service.container: Error enabling service: Error waiting for apis ["container.googleapis.com"] to be enabled for enocom-dev: googleapi: Error 403: The caller does not have permission, forbidden
* google_project_service.runtimeconfig: 1 error(s) occurred:

* google_project_service.runtimeconfig: Error enabling service: Error waiting for apis ["runtimeconfig.googleapis.com"] to be enabled for enocom-dev: googleapi: Error 403: The caller does not have permission, forbidden
* google_project_service.storage: 1 error(s) occurred:

* google_project_service.storage: Error enabling service: failed to issue request: googleapi: Error 403: The caller does not have permission, forbidden
* google_project_service.sql: 1 error(s) occurred:

* google_project_service.sql: Error enabling service: failed to issue request: googleapi: Error 403: The caller does not have permission, forbidden

This was apparently noted in hashicorp/terraform-provider-google#1579 and then fixed with hashicorp/terraform-provider-google#1632.

But the fix still isn't in the newest version of the Terraform GCP provider (v.0.14.0). Once the fix lands, we need to update this line to require the version with the fix.

[zombiezen]

Once the Terraform GCP provider updates, I'd also like to fix all the TODOs enabling the other services.

[zombiezen]

I've figured out a workaround for the time being: I can keep the service resources in place, but set them to count = 0. Then, once the new release is cut and we have confidence that we can flip it back on, we just remove the count = 0.

[zombiezen]

I can confirm that a dev build of hashicorp/terraform-provider-google@e123401 fixes this issue.