AWS::VpcLattice::Rule - HttpMatch Method not allowing `PATCH` or custom methods

### Name of the resource

Other

### Resource Name

AWS::VpcLattice::Rule

### Issue Description

When creating a VpcLattice Rule via API / CLI you can specify any HTTP request method, as per [VPC Lattice docs](https://docs.aws.amazon.com/vpc-lattice/latest/ug/listener-rules.html#listener-rule-conditions). When creating the resource via CloudFormation currently an error is received if the method is not in an allowed set of enum values. This does not include `PATCH`, or allow for custom values.

### Expected Behavior

Method property on AWS::VpcLattice::Rule HttpMatch should accept any string value.

### Observed Behavior

Currently allowed values are `CONNECT | DELETE | GET | HEAD | OPTIONS | POST | PUT | TRACE` as per [CloudFormation docs](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-vpclattice-rule-httpmatch.html#cfn-vpclattice-rule-httpmatch-method).

### Test Cases

Pass `PATCH` as the Method:
```
#/Match/HttpMatch/Method: #: only 1 subschema matches out of 2
#/Match/HttpMatch/Method: failed validation constraint for keyword [enum]
```

### Other Details

- https://docs.aws.amazon.com/vpc-lattice/latest/ug/listener-rules.html#listener-rule-conditions
- https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-vpclattice-rule-httpmatch.html#cfn-vpclattice-rule-httpmatch-method

Start with the AWS::VpcLattice::Rule HttpMatch Method property and compare the linked VPC Lattice and CloudFormation documentation. Check where the CloudFormation validation enum for this property is defined and how its resource-specification tests are run. Done means PATCH and custom HTTP methods pass validation instead of being rejected by the enum.

Written by the indexing model from the issue text.