DynamoDB tables exist even after deleting corresponding amplify application

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-console/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

arn:aws:amplify:eu-central-1:976089832919:apps/d36yi6n1dbxvrq

### Region

eu-central-1

### Amplify Console feature

Backend builds

### Describe the bug

I have noticed that aws resources are still used even after I deleted my amplify application

The example is DynamoDB's tables.

As you may see on screenshot there are a lot of tables of same name left from previous applications' tests

how to effectively clean the unused resource (not connected to app's arn) of my amplify applications, is there any special command like docker prune?

### Expected behavior

all assigned to amplify resources are detected and cleaned after app is deleted.
optionally: in case the resource is full of data like S3, the wizard must be provided to make owner decide what to delete.

### Reproduction steps

1) create new app
2) create backend data
3) delete the app
4) go to DynamoDB (or other resource service) and check the tables (or s3 buckets)

![Uploading Снимок экрана 2021-07-19 в 23.11.28.png…]()

### Build Settings

_No response_

### Additional information

_No response_

The report names no source file, test, or implementation entry point. Start by reproducing the create-backend/delete-app sequence in eu-central-1 and checking DynamoDB and S3 for remaining resources. Done means cleanup behavior is verified for deleted applications, with a safe decision path for resources containing data.

Written by the indexing model from the issue text.