Removal of unused resources in S3 bucket and better asset management

### Is this feature request related to a new or existing Amplify category?

_No response_

### Is this related to another service?

S3

### Describe the feature you'd like to request

Amplify CLI perform S3 actions to upload files such as current-cloud-backend while maintaining older unused assets in the S3 bucket, this incurs additional storage costs.

Additionally, Amplify performs recurrent s3 API calls when a resource has been updated, causing additional costs for the API calls. For example: when a small change has been performed on a lambda layer Amplify performs multiple API calls that replaces the existing layer while maintaining older version of the layer as well.

For users utilizing the free tier provided by AWS the usage of S3 for every update causes the limit to be reached very quickly.

### Describe the solution you'd like

Remove unused assets from S3 bucket and reduce the number of S3 API calls needed to perform updates.

### Describe alternatives you've considered

creating manual scripts that remove older assets

### Additional context

_No response_

### Is this something that you'd be interested in working on?

- [ ] 👋 I may be able to implement this feature request

### Would this feature include a breaking change?

- [ ] ⚠️ This feature might incur a breaking change

No files, tests, or entry points are named. Start by mapping the Amplify CLI paths that upload current-cloud-backend assets and update Lambda layers, then determine how unused S3 assets and repeated API calls are identified; done means obsolete assets are removed and updates reduce S3 calls without disrupting deployments.

Written by the indexing model from the issue text.