[AWS::WAFv2::WebACL] - [Coverage] - Add missing headerOrder property to WAFv2 WebACL FieldToMatch in CloudFormation

### Name of the resource

AWS::WAF::WebACL

### Resource name

_No response_

### Description

#### Description

The AWS WAFv2 API includes an optional headerOrder property in the FieldToMatch object, which allows users to specify the order of HTTP headers for inspection in WAF rules. However, this property is not currently present in the CloudFormation resource for WAFv2 WebACL's FieldToMatch

## References

### WAFv2 API Reference
- [FieldToMatch](https://docs.aws.amazon.com/waf/latest/APIReference/API_FieldToMatch.html)
- [HeaderOrder](https://docs.aws.amazon.com/waf/latest/APIReference/API_HeaderOrder.html)

### CloudFormation
[WAFv2 WebACL FieldToMatch](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-wafv2-webacl-fieldtomatch.html#cfn-wafv2-webacl-fieldtomatch-allqueryarguments)

This feature request is to add the missing headerOrder property to the WAFv2 WebACL FieldToMatch resource in CloudFormation. Adding this property would:
- Allow users to specify the order of HTTP headers for inspection in WAF rules directly through CloudFormation templates.

### Other Details

_No response_

Start by comparing the AWS WAFv2 API references for FieldToMatch and HeaderOrder with the CloudFormation WAFv2 WebACL FieldToMatch documentation linked in the issue. Done means the optional headerOrder property is supported and documented for CloudFormation templates; no repository file or test is identified in the issue.

Written by the indexing model from the issue text.