Move the editor.path to also allow "project level" setting rather than org level?

Currently `editor.path` is set at org level config. If it exists, I think all projects within the org "inherit" the ability to open in UE.

But I imagine, it may be the case, that some people do not want certain sites to be used within UE, therefore, it would be nice to be able to set editor.path at a project/sub-folder level rather than org level.

Start by tracing how the org-level `editor.path` setting is read and how project or sub-folder configuration is represented. Define the intended precedence and inheritance rules so individual sites can opt out, then verify the behavior across projects within one organization.

Written by the indexing model from the issue text.