fix(AWS Deploy): Handle error for abnormal CloudFormation stack state during AWS deployment

[archepro84]

An error that occurs when Serverless Deploy is forcibly terminated has been corrected.
When the status of the CloudFormation Stack is, REVIREW_IN_PROGRESS the code is configured to output an error message as discussed in the issue.

Closes: #11852

[medikoo]

@archepro84 thanks for addressing this. Before we take it, let's clarify few things:

What is the behavior currently (before this change), where exactly we crash, and what exactly is the error we receive?

[archepro84]

@medikoo

1. The corresponding code causes an error when the number of Stacks is less than 1 and there is an abnormal Stack, such as REVIEW_IN_PROGRESS, during the retrieval of CloudFormation's describeStacks in the serverless deploy command.
2. This error recognizes that the CloudFormation Stack already exists, and the ensureValidBucketExists method is executed.
   At this point, when attempting to retrieve the describeStackResource of CloudFormation using provider.request, the 'Error [ValidationError]: Resource ServerlessDeploymentBucket does not exist for stack' occurs, and normal business logic does not proceed.

[medikoo]

@archepro84, thanks for the additional explanations! Your proposal looks very good, please check my suggestions

[archepro84]

Thanks for your suggestions, @medikoo. I have reviewed all of your suggestions and left comments where necessary.

[medikoo]

Thank you @archepro84 ! We're getting closer

[medikoo]

Thank you 👍