feat: add vscode ext and settings

[juliusmarminge]

Add recommended vscode extensions and settings

• I reviewed linter warnings + errors, resolved formatting, types and other issues related to my work
• The PR title follows the convention we established conventional-commit
• I performed a functional test on my final commit

---

Shamefully stolen from @KATT's suggestion in #140.

---

[juliusmarminge]

Putting this up for discussion, both regarding if we include it or not, as well as what extensions we recommend?

[der-ofenmeister]

Think this goes programmer to programmer? I stick to the default Prettier plugin but someone might use eslint and husky, etc. - so that should be on them to config in their source?

[nexxeln]

Yeah I'm also on the side of not including it tbh. Not everyone uses vscode and I don't want to add a folder to a template which is just going to be deleted

[t3dotgg]

Two thoughts:

• This should recommend Tailwind vs code extension
• Prolly shouldn't recommend prettier b/c opinions

I think this fits in w/ using userId in session, it's common enough that it should probably be included and it doesn't hurt the people who choose not to use VS Code

[gcavanunez]

Though understandable the take on not including prettier due to getting into opinionated territory, wouldn't the out of the box eslint take from Next, the tailwindcss prettier plugin and the example that the create-t3-app uses prettier, be compelling arguments to include prettier?