docs(NODE-6854): update VS Code setup with extensions recommendations

[baruchiro]

Description

What is changing?

With writing the suggested extensions for VSCode, I added them as suggested, and VSCode will notify the user they are suggested for this project.

What is the motivation for this change?

Developer Experience and easier setup will help newcomers to join the project.

https://jira.mongodb.org/browse/NODE-6854

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

• Ran npm run check:lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[nbbeeken]

Thanks for lending a hand here @baruchiro, we don't think that these extensions are necessarily the most effective for contributors (minus eslint perhaps). The list found in our editor.md was written with onboarding members of our team in mind, justifying the use of git and pull request assistive extensions.

This has sparked the conversation about what we consider to be the baseline workflow for anyone working on this repo and how running the lint before committing is something we even struggle with. Perhaps, shared commit hooks that don't diminish the developer experience are something we need to investigate.