Fix #148: Adding .editorconfig and other VSCode recommendations (#146)

* Adding an editorconfig for default line-endings and spacing across all editors

* Added recommended extensions and settings for VSCode to ease shared dev environment

* File was missing a / in the initial comment line

* Update .editorconfig

Co-Authored-By: Tiberriver256 <Micah.rairdon@gmail.com>

Author: Tiberriver256

.editorconfig

@@ -0,0 +1,9 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+end_of_line = crlf
+charset = utf-8
+trim_trailing_whitespace = false
+insert_final_newline = true

.vscode/extensions.json

@@ -0,0 +1,3 @@
+{
+  "recommendations": ["EditorConfig.EditorConfig", "ms-vscode.PowerShell"]
+}

.vscode/settings.json

@@ -1,3 +1,4 @@
 {
-    "powershell.scriptAnalysis.settingsPath": "PSScriptAnalyzerSettings.psd1"
-}
+  "powershell.scriptAnalysis.settingsPath": "PSScriptAnalyzerSettings.psd1",
+  "editor.formatOnSave": true
+}

.vscode/tasks.json

@@ -1,4 +1,4 @@
-/ A task runner that invokes Pester to run all Pester tests under the
+// A task runner that invokes Pester to run all Pester tests under the
 // current workspace folder.
 // NOTE: This Test task runner requires an updated version of Pester (>=4.0.3)
 // in order for the problemMatcher to find failed test information (message, line, file).