fix(resource_dashboard): force recreate grafana_dashboard if uid changes

[paulojmdias]

Fixes: #2144

• Tests before the change

❯ TF_ACC=true TF_ACC_OSS=true GRAFANA_URL=http://localhost:3000 GRAFANA_AUTH="anonymous" GRAFANA_VERSION=11.6.1 go test -v ./internal/resources/grafana/ -run TestAccDashboard_uid_unset
=== RUN   TestAccDashboard_uid_unset
=== PAUSE TestAccDashboard_uid_unset
=== CONT  TestAccDashboard_uid_unset
    resource_dashboard_test.go:102: Step 2/3 error: Error running apply: exit status 1

         Error: [POST /dashboards/db][404] postDashboardNotFound {"message":"Dashboard not found","status":"not-found"}

          with grafana_dashboard.test,
          on terraform_plugin_test.tf line 3, in resource "grafana_dashboard" "test":
           3: resource "grafana_dashboard" "test" {

--- FAIL: TestAccDashboard_uid_unset (1.21s)
FAIL
FAIL	github.com/grafana/terraform-provider-grafana/v3/internal/resources/grafana	2.357s
FAIL

• Tests after this change

❯ TF_ACC=true TF_ACC_OSS=true GRAFANA_URL=http://localhost:3000 GRAFANA_AUTH="anonymous" GRAFANA_VERSION=11.6.1 go test -v ./internal/resources/grafana/ -run TestAccDashboard_uid_unset
=== RUN   TestAccDashboard_uid_unset
=== PAUSE TestAccDashboard_uid_unset
=== CONT  TestAccDashboard_uid_unset
--- PASS: TestAccDashboard_uid_unset (2.07s)
PASS
ok  	github.com/grafana/terraform-provider-grafana/v3/internal/resources/grafana	2.924s

[github-actions]

In order to lower resource usage and have a faster runtime, PRs will not run Cloud tests automatically.
To do so, a Grafana Labs employee must trigger the cloud acceptance tests workflow manually.

[paulojmdias]

Anyone can review this?

[radiohead]

Anyone can review this?

Hey @paulojmdias! Thank you for sending this PR, I'll take a look!

[paulojmdias]

Many thanks @radiohead 🙏

[radiohead]

Looks great, thank you! Sorry, I was busy and it took me a while to find time to review this.

[paulojmdias]

Thank you @radiohead! 🙌

I think the failed tests should be related with being a fork branch, but please confirm 🙏

[radiohead]

Thank you @radiohead! 🙌

I think the failed tests should be related with being a fork branch, but please confirm 🙏

Yes, you are correct. I'll get it merged in a bit, since everything works as expected and there aren't any differences in the setup for failing tests, so no need to do anything else from your side.