[ISSUE] Issue with `databricks_metastore` resource when renaming

[Gerrit-K]

Configuration

resource {
  name = "old-name"
}

Expected Behavior

When renaming the previously deployed metastore, the Databricks provider should actually rename the metastore.

Actual Behavior

When changing the name and applying the resource, the provider claims to apply the changed name, but the metastore keeps its old name and a subsequent plan/apply will cause the same diff again.

Steps to Reproduce

1. terraform apply
2. Change the name, e.g. to new-name
3. terraform apply -> claims that the operation was successful
4. terraform plan/terraform apply -> shows the same renaming again; when inspected via CLI or account console, you can still see the old name as well

Terraform and provider versions

OpenTofu v1.10.5
on darwin_arm64
+ provider registry.opentofu.org/databricks/databricks v1.87.1

Workaround

The metastore can be renamed via the CLI:

databricks metastores update <metastore-ID> --profile <profile> --new-name new-name

This operation really changes the name persistently.