Bug: Workspace creation is non-atomic

Just set up an Huly instance for my non-profit and the first time, I ran into a transactional issue.

My workspace would be "partialy" created because my S3 instance was not set up correctly.

The workspace creation seams to be a 2-steps action :

- Creation of mongodb collection
- Creation of associated bucket

In fact, my particular case is tied to misconfig, but to me, it means that this will happen in a situation where my S3 is simply not joinable for any reason.

Huly platform should implement a mechanism for handling a transactional state verification of the workspace creation to ensure consistency.

As the application system is mainly microservices oriented, I would suggest 2-phase commit, saga pattern or single local transaction.