[UX2.0] Transport IPv4 ACL variables are not working properly.

[tzarski0]

When you configure the following resource:

resource "sdwan_transport_feature_profile" "transport_profile_test" {
  name        = "transport_profile_test"
  description = ""
}

resource "sdwan_transport_ipv4_acl_feature" "transport_ipv4_acl_feature" {
  default_action     = "accept"
  description        = "control vpn 0 outbound traffic"
  feature_profile_id = sdwan_transport_feature_profile.transport_profile_test.id
  name               = "vpn0_acl_out"
  sequences = [
    {
      base_action = "accept"
      match_entries = [
        {
          destination_data_prefix_variable = "{{test}}"
        },
      ]
      sequence_id   = 1
      sequence_name = "acl"
    },
  ]
}

The first TF apply works OK, but the 2nd TF apply always shows the change:

  # sdwan_transport_ipv4_acl_feature.transport_ipv4_acl_feature will be updated in-place
  ~ resource "sdwan_transport_ipv4_acl_feature" "transport_ipv4_acl_feature" {
        id                 = "cd760664-34a2-47a8-b309-3d0cc02f32c6"
        name               = "vpn0_acl_out"
      ~ sequences          = [
          ~ {
              ~ match_entries = [
                  ~ {
                      + destination_data_prefix_variable = "{{test}}"
                    },
                ]
                # (3 unchanged attributes hidden)
            },
        ]
      ~ version            = 0 -> (known after apply)
        # (3 unchanged attributes hidden)
    }

The expected behavior would be for 2nd TF apply to show no changes. Same issue happens for source_data_prefix_variable. The fix we do here should work also for transport ipv6 acl and service ipv4/ipv6 acl.