[Bug] Inconsistent result on citrix_machine_catalog with non-default AWS VPC

[SLemonier]

Describe the bug

Summary of the issue
Creating a machine catalog on AWS on non-default VPC finishes with an error.

Terraform command (import, apply, etc): terraform apply
Resource impacted: machine catalog

Versions

Use the terraform -v command to find the Terraform and Citrix Provider versions.
Terraform: latest
citrix/citrix provider: latest
Operation system: macos 15.1

Terraform configuration files

resource "citrix_machine_catalog" "AAA-TF2" {
name = "AAA-TF2"
description = "Example multi-session catalog on AWS using Terraform"
zone = "zoneID"
allocation_type = "Random"
session_support = "MultiSession"
provisioning_type = "MCS"
minimum_functional_level = "L7_34"
provisioning_scheme = {
hypervisor = citrix_aws_hypervisor.RIC-AWS-EU-VDI-NPRD-TF.id
hypervisor_resource_pool = citrix_aws_hypervisor_resource_pool.NPRD-RIC-EUC-1A-TF.id
identity_type = "HybridAzureAD"
machine_domain_identity = {
domain = "domain.local"
domain_ou = "OU=DEV,OU=VDI,OU=EUAWS,OU=Citrix Servers,DC=domain,DC=local"
service_account = ""
service_account_password = ""
}
aws_machine_config = {
image_ami = "ami-01a0ae1aaa8156379"
master_image = "Windows_server-2022"
service_offering = "m7i.2xlarge"
security_groups = [
"fw-citrix-nprd-eu"
]
tenancy_type = "Shared"
}
network_mapping = [
{
network_device = "0"
network = citrix_aws_hypervisor_resource_pool.NPRD-RIC-EUC-1A-TF.subnets[0]
}
]
number_of_total_machines = 1
machine_account_creation_rules ={
naming_scheme = "S####"
naming_scheme_type ="Numeric"
}
}
}

Terraform console output

citrix_machine_catalog.AAA-TF2: Still creating... [57m0s elapsed]
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to citrix_machine_catalog.AAA-TF2, provider "provider["registry.terraform.io/citrix/citrix"]" produced an unexpected new value: .provisioning_scheme.network_mapping[0].network: was
│ cty.StringVal("10.68.236.192/26"), but now cty.StringVal("10.68.236.192`/26 (vpc-05d0f96b3f84d67ee)").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

CitrixIssueId: 59126