Offer dry run option for cdk destroy

### Describe the feature

It would be nice to see what the effect of using `cdk destroy` is without actually destroying anything. The ability to see a list of resources which would be destroyed during `cdk destory` perhaps at the same time validating the destroy would work would be useful.

### Use Case

We are establishing a destroy CI pipeline. As a significantly destructive operation, offering the ability to check what it will do prior to carrying out the destroy action would be very helpful.

### Proposed Solution

A dry run would show a list of resources to be destroyed, grouped by resource type and count, but not actually carry out a destroy action on anything. Flag via CLI, `cdk destroy --dry-run`

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.147.3

### Environment details (OS name and version, etc.)

Windows 10/latest Ubuntu GitHub actions runner

Start at the CDK CLI entry point for `cdk destroy` and trace how destroy validation and resource selection currently work. Define the dry-run behavior from the issue: report resources grouped by type and count, validate that destruction would work, and make no destructive changes; verify the result through the CLI's existing destroy checks.

Written by the indexing model from the issue text.