Feature request: Manually-defined workspace boundaries

[charles-dyfis-net]

The language server for Go, gopls, fails when working with nested modules in Helix with the following error (descriptions substituted for specific paths in italics):

The file is in location, which is a nested module in the project folder.

gopls currently requires one module per workspace folder.

Please open location as a separate workspace folder.

You can learn more here: https://github.com/golang/tools/blob/master/gopls/doc/workspace.md.

Presuming that I'm correct to understand that Helix currently has a hardcoded behavior where detected project root is also treated as a workspace root, and that only one workspace can exist at a time, the ability to override project root detection would make Helix practical to use with when developing nested Go modules, while being (presumably) much less difficult to implement than either adding multiple-workspace support to Helix or adding multi-module support to gopls.

[charles-dyfis-net]

As it turns out, this is the topic of extensive discussion in #4439, which appears to be heading towards near-future resolution.

I'd rather have an explicit override even in the presence of better autodetection logic, but the autodetection logic proposed therein will suffice. (In the interim, I'm relying on mkdir .git).