Resolve Workspace/devfile relationship and versioning

Problem to solve

As we move out of the initial spike phase of the remote development backend, we have some decisions that need to be made from a Product/UX perspective that will shape our path to production.

Specifically:

1. Should we keep the input for a Devfile/creation of a Workspace flexible (a text box input field) or is it always tied to a versioned Devfile thats checked into a GitLab repo?
2. What limitations do we place on users?
   1. Do they have a single namespace? Can this be used to provision a Workspace for a different namespace?
   2. Should we limit the creation of workspaces similar way as we do it with CI minutes
      1. You can commit to a project = you can create pipeline that will be billed to the project’s namespace
      2. You can commit to a project = you can start a workspace for that project that will be billed to the project’s namespace
3. Should users be allowed to edit the devfile for a running workspace from the GitLab UI?

Outcomes