Feature request: Support resource scoped settings

Hi,

I rely heavily on vscode's multi-root workspaces feature. However, when using multi-root workspaces I can only change settings for this extension across the entire workspace and not inside individual projects in the workspace.

When I set any of the extension settings inside the .vscode/settings.json file in my project, they're disabled and when I mouse over them I see this message:

This setting cannot be applied in this workspace. It will be applied when you open the containing workspace folder directly.

If I understand correctly, it seems like support has to be added to the extension itself:

You as extension author have to make the decision which scope applies to your settings:

Scope	Description
window	The setting is applied to the entire VS Code instance.
resource	The setting is applied depending on an active resource.

By default, all settings have the window scope, however, we encourage you to support settings on the resource scope. Settings that apply on the window level are not supported once they are defined within a workspace folder, and as soon as the user entered a multi-root workspace. Settings that apply on a resource level however are supported, and as such, each workspace folder can have different values for these settings.

https://github.com/Microsoft/vscode/wiki/Adopting-Multi-Root-Workspace-APIs#settings

Thanks!

Start with the extension settings described in the issue and compare their behavior with VS Code's multi-root workspace settings guidance. Use the project's settings declarations and .vscode/settings.json examples as the entry points; done means supported extension settings can be configured independently for each workspace folder without the scope warning.