chore: Add Visual Studio and VS Code Support

[ciband]

Proposed changes

Added .vs and .vscode to the .gitignore file to support Visual Studio and VS Code

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improve a current implementation without adding a new feature or fixing a bug)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Build (changes that affect the build system)
• Docs (documentation only changes)
• Test (adding missing tests or fixing existing tests)
• Other... Please describe: Development environment support

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING documentation
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

Fixes #47

[codecov-io]

Codecov Report

Merging #48 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #48   +/-   ##
=======================================
  Coverage   79.48%   79.48%           
=======================================
  Files          39       39           
  Lines         697      697           
  Branches       70       70           
=======================================
  Hits          554      554           
  Misses        112      112           
  Partials       31       31

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c0e7799...4557ad3. Read the comment docs.

[faustbrian]

@ciband Please start to follow the https://docs.ark.io/guidebook/contribution-guidelines/git-commit-guidelines.html guidelines. I always have to reword your commits before I merge them.

[ciband]

@faustbrian
Sorry about that. I completely missed the verb tense and case in the guidelines. We have slightly different guidelines for git in my day job. I will pay more attention going forward. Thank you.