[aws-ec2] Accidental Log Group creation when creating a VPC

### Describe the bug

When adding a VPC with:
`const vpc = new ec2.Vpc(this, 'SomeVpc');`

a Lambda function is created with the description:
`Lambda function for removing all inbound/outbound rules from the VPC default security group`
and immediately deleted after the deployment is finished.

The main problem this generates is that as a consequence of the Lambda, a Log Group is also created, with retention set to `never expire`.
When the stack is deleted, the Log Group remains.

### Regression Issue

- [ ] Select this option if this issue appears to be a regression.

### Last Known Working CDK Version

_No response_

### Expected Behavior

A way to configure log retention.

### Current Behavior

When the stack is deleted, the Log Group remains.

### Reproduction Steps

`const vpc = new ec2.Vpc(this, 'SomeVpc');`

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### CDK CLI Version

2.156.0 (build 2966832)

### Framework Version

_No response_

### Node.js Version

v22.9.0

### OS

OSX

### Language

TypeScript

### Language Version

_No response_

### Other information

_No response_

No source files or tests are mentioned. Start by reproducing the VPC creation with `new ec2.Vpc(this, 'SomeVpc')` and inspect the generated Lambda and Log Group resources; done means log retention is configurable and the Log Group does not remain unexpectedly after stack deletion.

Written by the indexing model from the issue text.