fix!: remove hardcoded gcp-beta in vpc sub-module

[mkhtse]

The use of google-beta was added to accommodate network_profile at the time. It's now GA and the hard-coded beta provider causes the return of URL for nework_profile https://www.googleapis.com/compute/beta/projects/....... when the actual URL from the infrastructure is
networkProfile: https://www.googleapis.com/compute/v1/projects ( v1 instead of beta)
you can validate that by running gcloud compute networks describe

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[imrannayer]

@mkhtse thx for the PR. We decided to keep beta provider in case if we need to add any other beta feature in future..

[mkhtse]

@mkhtse thx for the PR. We decided to keep beta provider in case if we need to add any other beta feature in future..

hi @imrannayer Thanks for the comment. Has any report the conflict related to the URL for network_profile returns beta instead of v1?

This is the problem i'm facing. we work with google, they applied a network profile to an existing VPC network. To sync the config I had to remove the resource from state and re-import it. The issue occurs when I match my TF config with the state file and infrastructure, where the URL return beta when it should be v1. This causes Force replacement for the network object and all the resources references the vpc network subsequently.

[imrannayer]

@mkhtse thx. Can u plz sign CLA?