aws-pipes: `CfnPipe` doesn't set the CloudWatch Log Group in AWS Console

### Describe the bug

I deployed this [EventbridgeStack](https://github.com/momentohq/client-sdk-javascript/blob/main/examples/nodejs/aws/eventbridge/infrastructure/lib/eventbridge-stack.ts) and then checked the configuration for one of the Pipes in the AWS Console.

I noticed something curious:


The CloudWatch log group appears as NOT selected in the UI, yet it is actually selected (otherwise, it wouldn’t function properly).

Let's double-check:
1. Open the dropdown menu and select the same log group specified in the `EventbridgeStack`.
2. Save the Pipe.
3. Run `cdk deploy` again.

You’ll observe that no changes are made, which indicates the log group was correctly applied despite the UI showing otherwise. This seems to be a UI bug that occurs when deploying via CDK, and it might also affect deployments through CloudFormation directly.

### Regression Issue

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

### Last Known Working CDK Version

_No response_

### Expected Behavior

See above.

### Current Behavior

See above.

### Reproduction Steps

See above.

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### CDK CLI Version

2.161.1

### Framework Version

_No response_

### Node.js Version

20.18.0

### OS

Ubuntu 22.04

### Language

TypeScript

### Language Version

_No response_

### Other information

_No response_

Start with the linked EventbridgeStack example and reproduce the CfnPipe deployment using CDK CLI 2.161.1, then inspect the Pipe in the AWS Console. Compare the configured CloudWatch log group with the deployed configuration and determine whether the discrepancy is in CDK or the console. Done means the source of the mismatch is identified and a repository-level fix or clear upstream limitation is documented.

Written by the indexing model from the issue text.