(custom-resource-handler): hardcoded partition in s3 auto-delete-objects-handler

[kaizencc]

Describe the bug

When the linter was turned on in custom-resource-handlers, it alerted us to this line that was introduced here that fails the linter rule @cdklabs/no-literal-partition. This is our own custom linter rule that makes sure that we do not hardcode the aws partition anywhere because there are other partitions that need to be considered.

aws-cdk/packages/@aws-cdk/custom-resource-handlers/lib/aws-s3/auto-delete-objects-handler/index.ts

Line 54 in c8de5be

Resource: [`arn:aws:s3:::${bucketName}/*`],

At best this is something that we need to scrutinize and document why we are allowing. At worst we need to fix this as a bug.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

No response

Expected Behavior

no literal partitions

Current Behavior

literal partition

Reproduction Steps

see code

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

latest

Framework Version

No response

Node.js Version

latest

OS

mac

Language

TypeScript

Language Version

No response

Other information

No response

[kaizencc]

Linting happened here: #33204

[ashishdhingra]

Issue opened by CDK team. Adding p2 as priority for now.