Marked terraform provider imports as v3

[melinath]

Related to GoogleCloudPlatform/terraform-validator#158. TLDR we need to do semantic versioning for the providers so that they can be imported as libraries (specifically by terraform-validator.) There are just a couple of spots in magic-modules that reference a package version, so we need to update those; otherwise, go will try to install v1 of the package alongside v3.

This has two companion PRs that update the module name for the two providers:

• Added v3 to module path hashicorp/terraform-provider-google#7982
• Added v3 to module path hashicorp/terraform-provider-google-beta#2770

This will not break people using the providers, because those are specially built binaries rather than terraform using the package as a library.

Release Note Template for Downstream PRs (will be copied)

[modular-magician]

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 1 file changed, 1 insertion(+), 1 deletion(-))
Terraform Beta: Diff ( 1 file changed, 1 insertion(+), 1 deletion(-))

[modular-magician]

I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=162552"

[c2thorn]

Am I understanding correctly that this was referring to an older version of the beta provider because we weren't following semantic versioning?

[melinath]

yes, that's correct. It was working nonetheless because it was all local to the module and had the same path as the module, but once the downstream PRs are merged the module name will include the v3 and any references to the old module name will result in version 1.20 being downloaded and used by those imports.