azurerm_kusto_script - Lock kusto cluster so multiple scripts can be applied

[mojanas]

Fixes #16471

$ make acctests SERVICE='kusto' TESTARGS='-run=TestAccKustoScript_multiple' TESTTIMEOUT='30m'
==> Checking that code complies with gofmt requirements...
==> Checking that Custom Timeouts are used...
==> Checking that acceptance test packages are used...
TF_ACC=1 go test -v ./internal/services/kusto -run=TestAccKustoScript_multiple -timeout 30m -ldflags="-X=github.com/hashicorp/terraform-provider-azurerm/version.ProviderVersion=acc"
=== RUN   TestAccKustoScript_multiple
=== PAUSE TestAccKustoScript_multiple
=== CONT  TestAccKustoScript_multiple
--- PASS: TestAccKustoScript_multiple (1412.46s)
PASS
ok      github.com/hashicorp/terraform-provider-azurerm/internal/services/kusto 1415.445s

Based off of #16649
The kusto scripts modify the underlying cluster configuration during apply, so we would want to lock the cluster instead of the database.

[mojanas]

Tagging @mbfrahry and @sinbai for visibility

[mbfrahry]

Hey @mojanas, this is nearly there but we need to lock the actual cluster id and not just the cluster name.

[mbfrahry]

LGTM!

[github-actions]

This functionality has been released in v3.6.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[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 contributions.
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.