Use a provider's stable version when bundling schemas

[dbanck]

This PR updates our schema bundling script to use the provider version installed by Terraform over the latest version from the registry.

The latest language server releases bundled a pre-release version for Cloudflare and other providers, because the registry API returns it as the latest release. Terraform does not use the registry API and will only install stable releases unless otherwise specified. We are now mirroring this behaviour when bundling schemas until the registry API provides a way to filter for stable releases.

Affected providers

aztfmod/azurecaf: registry version doesn't match installed version: 2.0.0-preview3 != 1.2.28. Using 1.2.28

cloudflare/cloudflare: registry version doesn't match installed version: 5.0.0-alpha1 != 4.45.0. Using 4.45.0

grafana/grafana-adaptive-metrics: registry version doesn't match installed version: 0.3.0-alpha.5 != 0.2.0. Using 0.2.0

kaleido-io/kaleido: registry version doesn't match installed version: 1.1.0-rc-5 != 0.2.15. Using 0.2.15

outscale/outscale: registry version doesn't match installed version: 1.0.0-rc.2 != 0.12.0. Using 0.12.0

paloaltonetworks/panos: registry version doesn't match installed version: 2.0.0-rc.1 != 1.11.1. Using 1.11.1

rubrikinc/polaris: registry version doesn't match installed version: 0.10.0-beta.6 != 0.9.0. Using 0.9.0

rancher/rke: registry version doesn't match installed version: 1.5.1 != 1.6.0. Using 1.6.0

siderolabs/talos: registry version doesn't match installed version: 0.7.0-alpha.0 != 0.6.1. Using 0.6.1

Closes hashicorp/vscode-terraform#1869

[ansgarm]

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.