Describe the bug

A feature release via #25437 (Serverless V2 support) breaks a common workaround for V2.

Workaround explained here: #20197 (comment)

Note that it has 21 likes, so likely there are many instances of this workaround in the wild.

However, when switching to the official solution from #25437, the instances change the ID and need to be recreated.

A question I raised in the PR is whether or not it is possible to retain the original IDs somehow. I don't see the need for them to change.

Example: #25437 (comment)

Expected Behavior

The instances not to be re-created.

Current Behavior

ID changes and the instance gets re-created.

Reproduction Steps

#25437 (comment)

Possible Solution

N/A

Additional Information/Context

#25437 (comment)

CDK CLI Version

latest

Framework Version

2

Node.js Version

16

OS

macOS

Language

Typescript

Language Version

TS 5

Other information

No response