Add to contributor guide Windows specific "things"

[rocco8773]

Since most packages/tools for package development are intended for a Linux framework, they work well for MacOS but not so much Windows. For example, Windows has three different terminals Command Prompt (default), Powershell, and Windows Subsystem for Linux (WSL). The make command has very limited function in the Command Prompt and does not work in Powershell, but works just fine in WSL.

I've been specifically developing on Windows lately just so I can understand its "limitations" for our users/contributors. I'd like to keep this issue open for awhile so we can collect aspects of development that are specific to Windows systems.

What I think we should include (so far)...

1. Terminal options for Windows
2. Virtual Environments venv
3. limitations of make
4. ...

[rocco8773]

Using "Windows Terminal" to work with all three windows terminal options (wsl, powershell, and command prompt).

[namurphy]

The only place where we use make is in the doc build, so it'd be good to put the stuff related to make in Windows in the documentation guide.