Testing - Add a test step check to verify a resource was NOT destroyed+recreated

[c2thorn]

Historically we have relied on manual log review to verify that a resource was updated in place vs simply destroyed/recreated. This leads to gaps where update functions are unintentionally untested, since the test will still pass when the resource is recreated.

We should provide a common test step check function that will verify that the resource was not destroyed during the current step. We should also document it here: https://github.com/GoogleCloudPlatform/magic-modules/tree/main/mmv1/third_party/terraform#update-tests

[melinath]

It would be great to provide guidance on how to ensure that you are not deleting a resource during the update test:

• Avoiding changes to ForceNew fields
• lifecyle.prevent_destroy = true

[rileykarson]

PlanCheck should allow us to assert this now: https://github.com/hashicorp/terraform-plugin-testing/releases/tag/v1.2.0

Sizing up since I think this requires switching to the new dedicated Go module.