HTTP backend not supported due to workspaces

[bl0way]

Describe the Bug

atmos should support the http backend as described here.
Unfortunately, the http backend is not inside of the workspace supported backend list and internally atmos is using workspace.

This is limiting for us as we would like to use atmos with GitLab that only support the http backend. This backend coupled with GitLab (I don't know other ones that well) is expecting to have different addresses to provide isolation instead of using workspaces. Maybe we could use templated variables from atmos to adjust this backend address?

There is an open issue for workspaces support on GitLab here.

Moreover OpenTofu is considering deprecating workspaces opentofu/opentofu#2160

Expected Behavior

Provide a way to setup the http backend with atmos.

Steps to Reproduce

Setup a classic http backend, then run an atmos terraform command. It should fail with workspaces not supported.

Screenshots

No response

Environment

No response

Additional Context

On Slack a feature flag to toggle usage of workspaces has been suggested to solve this issue.