Initial workspaces setup does not match a real life scenario: missing a "dev" workspace

As a developer / project creator, I can have 2 objectives when creating a project:

1. I want an app very quickly deployed
2. I want a full engineering setup (dev, test, prod) for a well-maintained application

### Expected Behaviour

During the project creation, I should be offered either just 1 workspace (`production` for quick app deployment) or 3 workspaces (`production`, `staging` and `dev` for a clean setup matching also the CI/CD provided)

### Actual Behaviour

When a project is created, 2 workspaces are proposed by default: `production` and `staging`.

If I did not follow a formal training or studied the doc, I do not change the workspace setup (= default is what I should need). Then when I use the cli to create the app and map it to my project, I am asked which workspace I should use: `production` or `staging` ?

1. If I want an app very quickly deployed, I do not know what to do with the `staging` workspace.
2. If I want a full engineering setup, either I know I am missing the `dev` workspace or I will select the `staging` which in the future will lead to confusion (how do I switch now to the `dev` workspace`). Also in this scenario, the CI/CD proposed by default is great, but `staging` and `production` are clearly not to be "touched" by a developer which makes the `dev` workspace mandatory.

Conclusion: whatever is your objective, the initial workspaces setup does not match a real life scenario: either the project creator has to delete the `staging` workspace or add a required `dev` namespace.

cc @meryllblanchet