Third Behavior Option for `deleteStack` Mutation to Abort Deletion if Managed Resources Exist

The client would like a third behavior option for the destroyResources parameter. This option would ensure that the stack is only deleted if it has zero managed resources; otherwise, the operation would fail or abort. Additionally, requesting clearer error messages and more comprehensive documentation for the GraphQL API to improve usability and understanding.