Change default on `google_project_service.disable_on_destroy` to false

[rileykarson]

As discussed in GoogleCloudPlatform/magic-modules#10636. The current default can be dangerous if there are multiple configurations in a project, and disabling services on destroy should probably be an explicit decision.

b/339530229

[roaks3]

@rileykarson this just popped up as an issue we couldn't forward, because our current forwarding behavior expects another type label. From my understanding, this looks like a feature request to improve usability, but we can change if that's incorrect.

[Splizard]

Just an experience report here, if you create a submodule and use it for each cloud run service you want to represent. If you added google_project_service for the cloud run API in the submodule, to make sure the API is enabled and then later decide to remove a single service, terraform/GCP will rather unexpectedly nuke all of your cloud run services without any indication in the terraform plan.

I was a bit shocked to discover there is a disable_on_destroy property that defaults to true and has this effect.