The rule type of ip_set_reference_statement isn't extended to support additional arguements

[wesleykirkland]

What is the current behavior?
ip_set_reference_statement doesn't have the ability to input ip_set_forwarded_ip_config as a statement inside of it.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
The following is custom input to the module though validated.

The supported logic can be seen here - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/wafv2_rule_group#ip-set-reference-statement

global-rule1 = {
      envs_to_apply = ["dev", "stg"]
      rule = {
        name     = "global-rule1"
        priority = "11"

        action = "allow"

        visibility_config = {
          cloudwatch_metrics_enabled = false
          metric_name                = "global-rule1-metric"
          sampled_requests_enabled   = false
        }

        ip_set_reference_statement = {
          arn = aws_wafv2_ip_set.global_OfficeCidr.arn
          ip_set_forwarded_ip_config = {
            fallback_behavior = "NO_MATCH"
            header_name       = "X-Forwarded-For"
            position          = "ALL"
          }
        }
      }
    }

You can see here that the logic isn't supported.

What is the expected behavior?
ip_set_forwarded_ip_config should be supported.

Software versions?
3.8.1