feat: Added cookiecutter support and docs for VSCode debugging

[kgpayne]

Added module entry point to tap and target cookiecutters, and guidance on how to use them for debugging in VSCode.

---

📚 Documentation preview 📚: https://meltano-sdk--968.org.readthedocs.build/en/968/

[edgarrmondragon]

@kgpayne nice! Left a few suggestions

[codecov]

Codecov Report

Merging #968 (8c436e8) into main (f74493d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #968   +/-   ##
=======================================
  Coverage   81.77%   81.77%           
=======================================
  Files          37       37           
  Lines        3742     3742           
  Branches      746      746           
=======================================
  Hits         3060     3060           
  Misses        500      500           
  Partials      182      182           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[edgarrmondragon]

@kgpayne wdyt about adding the .vscode/launch.json file to the tap cookiecutter, perhaps conditioned on a new question?

[kgpayne]

@kgpayne wdyt about adding the .vscode/launch.json file to the tap cookiecutter, perhaps conditioned on a new question?

I don't have a strong sense of how popular vscode is relative to others like pycharm/vim/sublime/atom 🤔 @tayloramurphy do we have any IDE data from our user surveys?

Either way, I think adding docs/instructions for 1 or 2 other IDE's might be a good next step, then adding a new cookie cutter question when there are a couple of options to choose from 🙂 @pandemicsyn uses pycharm so may be able to contribute a snippet for that, and I believe @cjohnhanson uses vim.

Edit: created #973 to track additional IDE setup docs