(aws-ec2): NAT Gateway error while CIDR replacement in VPC

### What is the problem?

NAT Gateway not attached while CIDR changed and causing CloudFormation stack update failed.

> Failed resources:
UPDATE_FAILED | AWS::EC2::NatGateway | vpc/publicSubnet1/NATGateway (vpcpublicSubnet1NATGateway) NatGateway nat-xxxxxxxx is in state failed and hence failed to stabilize. Detailed failure message: Network vpc-xxxxxx has no Internet gateway attached

### Reproduction Steps

replace the CIDR with something else like 10.20.0.0/16 then run deploy will trigger this issue.

```
const cidr = '10.10.0.0/16';
this.vpc = new ec2.Vpc(this, 'vpc', {
cidr: cidr,
enableDnsHostnames: true,
enableDnsSupport: true,
maxAzs: 2,
natGateways: 1,
flowLogs: {
FlowLog: {
destination: ec2.FlowLogDestination.toS3(s3Bucket),
},
},
subnetConfiguration: [
{
name: 'public',
subnetType: ec2.SubnetType.PUBLIC,
cidrMask: 24,
},
{
name: 'private',
subnetType: ec2.SubnetType.PRIVATE_WITH_NAT,
cidrMask: 24,
},
],
});
```

### What did you expect to happen?

This should creating a new NAT Gateway and switch from old resource to the new one.

### What actually happened?

the following error message.

> Failed resources:
UPDATE_FAILED | AWS::EC2::NatGateway | vpc/publicSubnet1/NATGateway (vpcpublicSubnet1NATGateway) NatGateway nat-xxxxxxxx is in state failed and hence failed to stabilize. Detailed failure message: Network vpc-xxxxxx has no Internet gateway attached

### CDK CLI Version

1.53.0 (build 6c326cb)

### Framework Version

_No response_

### Node.js Version

v15.13.0

### OS

MacOS 10.14.6

### Language

Typescript

### Language Version

_No response_

### Other information

_No response_

Start with the TypeScript ec2.Vpc construct and its public-subnet NAT Gateway configuration, then reproduce the CIDR replacement deployment described in the issue. Done means the update creates and switches to a new NAT Gateway without failing because the VPC lacks an Internet Gateway.

Written by the indexing model from the issue text.