[BUG] Failed when executing plan due to changeSet name is invalid

[dromero-cibernetica]

Describe the bug
In v1.1.8 when executing plan it fails trying to execute the changeSet operation due to a constraint in value of the changeSet name. When executing in 1.1.7 the name uses dash (-) instead of underscore and no problems

To Reproduce
Steps to reproduce the behavior:

1. How you installed ECS ComposeX'...' Created the docker image and run the container
2. How you are executing it ? : As a CLI tool, as a library, in lambda? Executing as a cli inside a docker
3. Link / share your Docker compose file: Any docker-compose.yaml
4. See error:
   docker run -u 0:0 -it --env-file /tmp/.awsenv --rm -v /root/.aws:/tmp/.aws -e HOME=/tmp -v $PWD:/tmp compose-x/compose-x:v1.1.8 plan --name xtest --format yaml -d cfn.templates.d -f docker-compose.yaml -f aws-compose.yaml

botocore.exceptions.ClientError: An error occurred (ValidationError) when calling the CreateChangeSet operation: 1 validation error detected: Value 'xtest_ecs_compose_x_1758584792' at 'changeSetName' failed to satisfy constraint: Member must satisfy regular expression pattern: [a-zA-Z][-a-zA-Z0-9]*

Expected behavior
Execute plan accordingly. It works in v1.1.7

Desktop (please complete the following information):

• OS: [e.g. Fedora/Windows/Mac]: Amazon Linux 2023
• Python version (3.6,3.7,3.8): Python 3.10
• If you were doing things from a branch, which one? main (HEAD detached at v1.1.8)
• Commit ID ? d668880
• Tag/Version? v1.1.8

[JohnPreston]

@dromero-cibernetica If you would please check from the main branch that this works out for you so I would publish 1.1.9? Thanks

[dromero-cibernetica]

It did work and fixes x-tags also
Thanks!