[Bug] Invalid reordering when using capitalized role names on User and Service Account resources

[briankassouf]

Describe the bug

When using capitalized role names (e.g. Admin) in the namespace access set the plan can sometimes result in an unnecessary, invalid planed change. This affects both the User and Service Account resources.

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following
symbols:
  ~ update in-place

Terraform will perform the following actions:

  # temporalcloud_service_account.namespace_admin will be updated in-place
  ~ resource "temporalcloud_service_account" "namespace_admin" {
        id                 = "..."
        name               = "sa-name"
      ~ namespace_accesses = [
          - {
              - namespace_id = "terraform" -> null
              - permission   = "read" -> null
            },
          - {
              - namespace_id = "terraform2" -> null
              - permission   = "write" -> null
            },
          + {
              + namespace_id = "terraform"
              + permission   = "Read"
            },
          + {
              + namespace_id = "terraform2"
              + permission   = "Write"
            },
        ]
        # (2 unchanged attributes hidden)
    }

I believe this is due to an issue upstream hashicorp/terraform-plugin-framework#1061.

Additional context

Current work around is to use lower cased role names when configuring the User and Service Account resource. For example, prefer admin over Admin.