Fix | Issue with Project Name and Longname in Leverage CLI

[exequielrafaela]

Describe the Bug:

When a project name (or "longname") with spaces is used in the Leverage CLI during the Landing Zone bootstrap deployment process here https://leverage.binbash.co/try-leverage/ , it creates directories with spaces in their names. This leads to a series of problems as the directories are not handled correctly due to the spaces.

Previous issue was reported by @juanmatias and could be find here: #145

Expected Behavior:

The expected behavior is that the CLI should either reject project names or longnames with spaces or handle them correctly without causing any issues. Alternatively, the CLI could use only the shortname for directory names.

Steps to Reproduce:

1. Run the Leverage CLI with a project name or longname that includes spaces.
2. Observe that the CLI creates directories with spaces in their names during the https://leverage.binbash.co/try-leverage/leverage-project-setup/ process.
3. Notice the resulting issues due to the spaces in the directory names when running leverage terraform init commands and other similar ones.

Environment:

OS: Linux
Version: Latest

Additional Context:

A potential solution could be to enforce valid characters for directory names in the CLI or to use only the shortname for directory names. This issue needs to be addressed to prevent problems when using project names (or longnames) with spaces.