(aws-sqs): default encryption of `SSE-SQS` is not explicitly set

### Describe the bug

Right now, an SQS Queue [has `SQS_MANAGED (SSE-SQS)` enabled by default](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_sqs.Queue.html#encryption). This, however, is [implicit](https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-sqs/lib/queue.ts#L399) and should be explicit, setting the same properties as if `SQS_MANAGED` was [explicitly set](https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-sqs/lib/queue.ts#L434).

### Expected Behavior

I expect the default Queue to create a CFN Resource with the the following property: `sqsManagedSseEnabled: true`

### Current Behavior

There is no `sqsManagedSseEnabled: true` property set, instead it assumes SSE-SQS is enabled *at the region*.

### Reproduction Steps

Create a SQS queue and examine its CFN output.

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### CDK CLI Version

2.70

### Framework Version

_No response_

### Node.js Version

16.3.0

### OS

Mac

### Language

Python

### Language Version

_No response_

### Other information

_No response_

Read packages/aws-cdk-lib/aws-sqs/lib/queue.ts at the linked lines, comparing the default encryption path with the explicit SQS_MANAGED path. Reproduce the issue by synthesizing a default SQS Queue and inspecting its CloudFormation output; done means the output includes sqsManagedSseEnabled: true.

Written by the indexing model from the issue text.