CloudFormation - Create / Update stacks dose not surface stack errors in logs

**Describe the bug**
When the Cloudformation create / update stack task fails the API response with the offending Logical ID and Status reason is not surfaced in the task logs. it is not possible to debug the error from the release and requires the user to retrieve the errors direct from Cloudformation manually.

**To reproduce**
create a cfn template with an error and deploy using the cloud formation create stack task. the the task is run and fails. the actual error is not surfaced. the task logs only states that the task is in the wrong state.

**Expected behavior**
create a cfn template with an error and deploy using the cloud formation create stack task. the the task is run and fails. the Logical ID and the Status reason will be printed to the logs.

**Your Environment**
- Azure Devops cloud based

Reproduce the failure with an AWS CloudFormation create or update stack task using a template error, then inspect how the task handles the API response and writes task logs. Done means failed deployments print the offending Logical ID and Status reason instead of only reporting an incorrect task state.

Written by the indexing model from the issue text.