feat(cli): warn the user of resource renaming

[otaviomacedo]

TL;DR: with this feature, the CLI will detect when resources have been renamed
and ask the user if they really want to deploy the stack, considering that it will
cause resource replacement.

For now, it's just an additional barrier, to help protect against accidental
renaming. But in the future (possibly with the help of CloudFormation), we can
actually perform the refactoring on the user's behalf. Also, we are only checking
the simplest case, where the logical ID changes, but the resource is kept as it
was. Future work may include:

• Computing a distance function between resources, and then interact with the
  user to establish what is renaming and what is actual replacement.
• Storing metadata based on this interaction to apply the change in other
  environments without user interaction (e.g., CI/CD).

Reproducing the relevant part of the README below for convenience.

---

If you change the ID of a construct, this change will be propagated all the
way down to the CloudFormation level, leading to the change of at least one
resource logical ID. If you then use this template to update a stack created
with the previous version of the template, all the renamed resources will be
replaced.

Since a renaming like this might have happened by accident, the CLI will detect
such cases just before performing a deployment, and ask for confirmation to go
ahead. For example, suppose you have the following construct tree:

MyStack
└ MyBucket
  └ Resource 

In the template, the bucket resource will have a logical ID like
MyBucketFD3F4958. So you deploy this template for the first time, creating
the stack. Then you decide to rename the MyBucket construct to NewName
and try to deploy it again, to update the stack. Since the logical ID has
changed (to something like NewNameEF569C1A), the CLI will prompt you with
the following message:

Some resources have been renamed:
  - MyStack/MyBucket/Resource -> MyStack/NewName/Resource

Do you wish to deploy these changes (y/n)?

Notice that it displays the CDK metadata path for the resource. If this
field is not present, it will use the logical ID instead.

Resources are considered equal if they have the same content (up to reordering
of properties). So if you have different logical IDs referring to equal objects,
and you rename at least two of them, it's impossible to establish a 1:1
correspondence as above. So the CLI will display a correspondence between sets
of identifiers:

Some resources have been renamed:
  - {MyStack/MyBucket1/Resource, MyStack/MyBucket2/Resource} -> 
  {MyStack/NewName1/Resource, MyStack/NewName2/Resource}

Do you wish to deploy these changes (y/n)?

As usual, you can force the CLI to skip this approval with the
--require-approval nevel option.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ CLI code has changed. A maintainer must run the code through the testing pipeline (git fetch origin pull/33257/head && git push -f origin FETCH_HEAD:test-main-pipeline), then add the 'pr-linter/cli-integ-tested' label when the pipeline succeeds.

If you believe this pull request should receive an exemption, please comment and provide a justification. A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed, add Clarification Request to a comment.

[codecov]

Codecov Report

Attention: Patch coverage is 95.58824% with 3 lines in your changes missing coverage. Please review.

Project coverage is 80.91%. Comparing base (c346e82) to head (e3f0a52).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #33257      +/-   ##
==========================================
+ Coverage   80.84%   80.91%   +0.06%     
==========================================
  Files         232      233       +1     
  Lines       14135    14197      +62     
  Branches     2460     2469       +9     
==========================================
+ Hits        11428    11487      +59     
- Misses       2427     2430       +3     
  Partials      280      280              

Flag	Coverage Δ
suite.unit	80.91% <95.58%> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
packages/aws-cdk	79.76% <95.58%> (+0.12%)	⬆️
packages/aws-cdk-lib/core	82.17% <ø> (ø)

[aws-cdk-automation]

➡️ PR build request submitted to test-main-pipeline ⬅️

A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: e3f0a52
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mrgrain]

Please move to api/refactoring.ts dvd the test file accordingly.

[mrgrain]

This will need to be added to the new Toolkit as well (yes I now it's annoying).