(deploy) support best-effort stack deployment

### Describe the feature

Reopening aws/aws-cdk#22516. The rationale provided by @indrora is irrelevant. It is already the case that CDK considers each stack to be independent - if one fails it does not make any attempt to roll back any that were already deployed.

Currently if a stack fails during `cdk deploy` then that stack is reverted and any remaining ones are aborted. Instead, there should be a flag to do a best-effort deployment, meaning that if a stack fails:
1. that stack gets rolled back
2. other stacks that depend on it (directly or indirectly) are skipped
3. all remaining stacks continue to deploy normally
4. the `cdk deploy` command itself still fails at the end

### Use Case

Sometimes `cdk deploy` can fail for arbitrary reasons, like hitting an account limit, or getting throttled. In these situations it would be better to be able to allow the deployment to proceed as much as possible.

### Proposed Solution

_No response_

### 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.39.1

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

Alpine 3.16, Python 3.10.6