Supported resource AWS::EC2::VPCGatewayAttachment can't be imported to stack

### Name of the resource

Other

### Resource Name

AWS::EC2::VPCGatewayAttachment

### Issue Description

Existing resource AWS::EC2::VPCGatewayAttachment can't be imported to stack. There is a weird error with such description:
`READ operation is not supported`

### Expected Behavior

Reffering to:
https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/supported-resources.html
and
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/resource-import-supported-resources.html
Resource is supported by import. So, I should be able to import this resource into my cloudformation stack.

### Observed Behavior

Existing resource AWS::EC2::VPCGatewayAttachment can't be imported to stack. There is a weird error with such description:
`READ operation is not supported`

### Test Cases

I used such template file to import this resource:
```
Resources:
...
VpcVPCGWBF912B6E:
Type: AWS::EC2::VPCGatewayAttachment
Properties:
InternetGatewayId:
Ref: VpcIGWD7BA715C
VpcId:
Ref: Vpc8378EB38
DeletionPolicy: Retain
Metadata:
aws:cdk:path: CommonVpcStack/Vpc/VPCGW
...
```
And here is the import.json file that I provide with the template when creating a change set:
```
...
{
"ResourceType":"AWS::EC2::VPCGatewayAttachment",
"LogicalResourceId":"VpcVPCGWBF912B6E",
"ResourceIdentifier": {
"AttachmentType":"IGW",
"VpcId":"vpc-xxxxxxxxxxxxxxxxx"
}
},
...
```
I removed redundant information from it

### Other Details

_No response_

Start by reviewing the CloudFormation resource-import documentation linked in the issue, then reproduce the behavior with the shown template and import.json entry for AWS::EC2::VPCGatewayAttachment. Done means confirming whether the documented import support matches the observed READ operation error and documenting or resolving that discrepancy.

Written by the indexing model from the issue text.