Allows naming which quick fixes should be run on save

[adenflorian]

Implements #152 .

Feedback welcome 😄

[egamma]

@adenflorian thanks for the Pull Request. Looks good overall (you also changed the formatting rules which makes sense, since it adds minimal noise to the PR the formatting change is tolerable).

• What is the reasoning behind the changes to the settings.json in tslint-server/.vscode/settings.json
• You have added tslint/package-lock.json, which hints that you are using npm v5. Any things to consider when upgrading to npm v5?
• Would be better if we could provide intellisense on the rule names and do some validation (but this is currently not support by the core vscode).

I'm currently in the middle of migrating the settings support of vscode-tslint for the new multi-root workspaces. This will take longer. I'll look into merging this PR before these changes before the other changes. So if there are delays you know why.

[egamma]

Decided to merge it in before the multi-root work. Published as 0.17.0, thanks again.

[adenflorian]

@egamma

• I added the formatting rules to the workspace settings so that my user settings wouldn't change the format of the whole document.

• This was the first time I've seen the package-lock.json, so I'm new to the idea, but it seems to "optimize the installation process".

• Agreed. I looked to see if any of the existing config for the extension did this, but it didn't seem to, so I decided to leave it for a separate enhancement/PR.