feat: add provider version to metadata generation

[qz267]

Feature request from: b/356844884

Add ProviderVersion to metadata auto generation. Changes including:

• Added parseBlueprintProviderVersions function to tfconfig.go
• Added TestTFProviderVersion to tfconfig_test.go
• Wired up parseBlueprintProviderVersions to getBlueprintRequirements function, which was called in the metadata generation process.
• Update golden-metadata.yaml requirements block, added provider versions block.

Checks:

• make go_test passing
• make int_test passing
• make docker_go_lint passing

[bharathkkb]

Thanks for the PR @qz267! Few minor comments

[qz267]

@bharathkkb a friendly ping, all the comments addressed, this PR ready for another review.

[bharathkkb]

Thanks for updating, just two last comments

[qz267]

hmm, rerun the unit tests on local branch multiple times, all passing, might need to rerun the action job?

[apeabody]

This is from the CFT CLI Test:

Error! Generated metadata(s) do not match the golden(s).
diff --git a/metadata.yaml b/metadata.yaml
index ffb9656..6059145 100644
--- a/metadata.yaml
+++ b/metadata.yaml
@@ -250,7 +250,7 @@ spec:
       - compute.googleapis.com
       - serviceusage.googleapis.com
     providerVersions:
-      - source: hashicorp/random
-        version: ">= 2.1"
       - source: hashicorp/google
         version: ">= 4.42, < 5.0"
+      - source: hashicorp/random
+        version: ">= 2.1"

Looks like maybe update the line ordering in cli/bpmetadata/int-test/goldens/golden-metadata.yaml?

[qz267]

Updated golden metadata yml provider data.

[bharathkkb]

@qz267 I missed that RequiredProviders output was coming from a map. It would be good to stable sort this to prevent any kind of diffs in the future due to ordering.