Add support for reading relative paths in settings in .code-workspace file

[karrtikr]

When using ${workspaceFolder} or . notation in settings inside a .code-workspace file, For eg.

{
    "folders": [
        {
            "path": "notpython" // not a python folder
        },
        {
            "path": "python1" // the python folder that contains .pylintrc
        },
        {
            "path": "python2" // the python folder does NOT contain .pylintrc
        },
        {
            "path": "." // root workspace parent of both python1 and python2
        }
    ],
    "settings": {
        "pylint.args": ["--rcfile=${workspaceFolder}/.pylintrc"],
        "python.defaultInterpreterPath": "./.venv/bin/python"
    }
}

We should resolve that setting differently for each workspace folder. For eg. the value of that setting will be <path_to_notpython>/.pylintrc for first workspace folder, whereas <path_to_python1>/.pylintrc for the second one. Same goes when using . instead of ${workspaceFolder}.

cc/ @karthiknadig I'm not sure if we should resolve . for all settings, but at least for python.defaultInterpreterPath setting this seems ok

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[karrtikr]

This applies for all extensions and should be ideally supported by VS Code. We can transfer it upstream if needed based on the upvotes.

[karrtikr]

Opened microsoft/vscode#198158 for the general support on VS Code.

[brettcannon]

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue.