bug: CFn stack name creation standards not set

[deepak2431]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

AWS only allows a stack name to declared with following characters
"Stack name can include letters (A-Z and a-z), numbers (0-9), and dashes (-)."

In localstack, there's no validation of stack name while creating it. Creating a stack with the name s3_bucket also successfully creates one.

Expected Behavior

While creating a stack with stack name which doesn't follows the standard, it should throw out an error with the message.

How are you starting LocalStack?

With the localstack script

Steps To Reproduce

How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)

python -m localstack.cli.main start --host

Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

`awslocal cloudformation deploy --stack-name test_s3_bucket --template-file "cfn_iam.yaml"`

This command with an invalid stack name also creates an stack successfully.

Environment

- OS: macOS
- LocalStack:

Anything else?

No response

[localstack-bot]

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

[deepak2431]

I can take up this issue to work on after the issue status is confirmed.

[dominikschubert]

Implemented in #8166