VSCode update editor config

[o-l-a-v]

PR Summary

I use VSCode for contributing to this project, and I found some outdated settings and extensions I'd like changed for a better dev experience. I'd be interested to hear what the project maintainers thinks about these suggestions. 🙂

Related issues

• 1674

Extensions changes

When opening the repo in VSCode it recommends extensions:

• fudge.auto-using: Deprecated according to https://github.com/natanfudge/Auto-Using and implemented in OmniSharp since https://github.com/OmniSharp/omnisharp-roslyn/issues/1482.
• ms-vscode.powershell-preview: ms-vscode.powershell has built in ability to enable preview version, ms-vscode.powershell-preview no longer exist.
• Added EditorConfig.EditorConfig for #1674

Config changes

• Tell VSCode not to create SLN file in VSCode workspace automagically, ref https://github.com/microsoft/vscode-dotnettools/issues/31.
• Change deprecated setting engineLogging to logging.diagnosticsLog.protocolMessages.
• Added initial .editorconfig file as a starting point for #1674, "stolen" straight from https://github.com/PowerShell/PowerShell/blob/master/.editorconfig.

PR Context

See PR summary.

PR Checklist

• [x] PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• [x] Summarized changes
• [x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• [x] This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • [x] None
  • OR
  • [ ] [Documentation needed]()
    • [ ] Issue filed:
• User-facing changes
  • [x] Not Applicable
  • OR
  • [ ] [Documentation needed]()
    • [ ] Issue filed:
• Testing - New and feature
  • [x] N/A or can only be tested interactively
  • OR
  • [ ] Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • [x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • [ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[alerickson]

@o-l-a-v everything looks appropriate, thanks for the suggestions and PR!