FR: Make Zephyr path setting overridable in workspaces

[devanlai]

Hi, I've been using this extension while learning the in's and out's of Zephyr's flavor of Devicetree and it's been a great help.

One thing that I noticed is that it's not possible to set the Zephyr location on a per-workspace basis, only on a per-machine basis.
I sometimes work with different versions of Zephyr (mainline Zephyr vs the nRF Connect SDK version of Zephyr) and it would be nice if I had the option to set it differently for specific workspaces so that I can be sure I'm working with the right set of devicetree files.

From some cursory testing, it seems like setting the scope on devicetree.zephyr to machine-overridable instead of machine would accomplish this.

[trond-snekvik]

Sorry for the delay, this slipped through the cracks. This is a bug. I'll resolve it in the next release.

[aunsbjerg]

Just a +1 for this feature, I work almost exclusively in workspace specific zephyr forks, so not being able to set the zephyr root is a bit of dealbreaker for this extension.