Description
When creating or updating a Google Analytics 4 Export connector using the Fivetran provider in a GitHub Actions CI/CD pipeline, Terraform reports an inconsistent result error specifically related to the `service_account_key` sensitive attribute. This makes it impossible to automate the deployment of GA4 connectors through CI/CD.

Environment
- Operating System: Ubuntu-latest
- CI/CD: GitHub Actions
- Provider Version: 1.2.4

Configuration

resource "fivetran_connector" "google_analytics_4_export" {
  group_id = "example_group_id"
  service  = "google_analytics_4_export"

  destination_schema {
    name = "google_analytics_4_export"
  }

  config {
    project_id  = "example-project"
    dataset_id  = "example_dataset"
    bucket_name = "example-bucket"
    service_account_key = jsonencode({
      "type": "service_account",
      // ... other standard GA4 service account fields ...
    })
  }

  lifecycle {
    ignore_changes = [
      config
    ]
  }
}

Error Message

Error: Provider produced inconsistent result after apply

When applying changes to fivetran_connector.google_analytics_4_export,
provider "provider[\"registry.terraform.io/fivetran/fivetran\"]" produced an
unexpected new value: .config.service_account_key: inconsistent values for
sensitive attribute.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Expected Behavior
The connector should be created/updated successfully in CI/CD pipelines, allowing for automated deployments.

Actual Behavior
The provider reports an inconsistent result error specifically related to the sensitive `service_account_key` attribute, causing CI/CD pipelines to fail. This occurs even when using lifecycle blocks to ignore changes.

Steps to Reproduce
1. Set up a GitHub Actions workflow with Terraform
2. Configure the Fivetran provider with valid credentials
3. Create a GA4 Export connector resource as shown above
4. Run the CI/CD pipeline
5. Observe the inconsistent result error during the apply phase

Additional Context
- The error persists even when using different variations of the `lifecycle` block (including `ignore_changes = config.service_account_key`).
- The configuration follows the structure shown in the Fivetran API documentation: https://fivetran.com/docs/rest-api/api-reference/api-configuration/connector-configuration#googleanalytics4export
- This issue specifically impacts automated deployments through CI/CD, making it impossible to manage GA4 connectors through Infrastructure as Code