Provider consistently flags changes for sensitive parameters in `avi_gslb`

[jakauppila]

Describe the bug

When managing an avi_gslb resource, the sites block repeatedly triggers in-place updates on sensitive parameters. Even though the configuration may not have changed, Terraform consistently detects that fields are replaced with actual passwords.

Related to #619 and #621

Reproduction steps

1. Configure a avi_gslb resource in Terraform with user/password in sites block
2. Run Terraform apply
3. Run terraform plan again without making changes to the terraform configuration
4. Observe that Terraform still detects a change in the sites block, prompting an update in-place.

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:

  # avi_gslb.site will be updated in-place
  ~ resource "avi_gslb" "site" {
        id                           = "https://controller.contoso.com/api/gslb/gslb-f0ffadd2-204e-4262-8643-86a5a0b64c2a"
        name                         = "Default"
        # (13 unchanged attributes hidden)

      ~ sites {
            name             = "nonprod"
          ~ password         = (sensitive value)
            # (10 unchanged attributes hidden)

            # (5 unchanged blocks hidden)
        }

        # (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Expected behavior

Terraform should recognize no actual difference if the password values remain the same as previously applied. The state should maintain the resource without forcing an update simply because the fields are treated as sensitive.

Additional context

Environment:

• Terraform v1.8.0
• terraform-provider-avi v30.2.2
• AVI 30.2.2