chore: add VS Code configuration for the project

[okineadev]

Description

Added necessary vscode extensions and settings for a flawless development experience

[brc-dd]

We all are using different stuff in vscode settings. And not everyone on the team is even using vscode or copilot. Checking .vscode to source control becomes problematic in longer run. I personally get annoyed by unstaging my custom settings every time I'm committing something.

Funding related changes can be kept but rarely any project in the organization (except I think Eduardo's) have that. And it probably should link to Vue's open collective instead. Also I believe no one actually runs npm fund ever.

[okineadev]

We all are using different stuff in vscode settings. Checking .vscode to source control becomes problematic in longer run. I personally get annoyed by unstaging my custom settings every time I'm committing something.

Then if you often encounter such problems, then it is exclusively a problem of your global vscode config

Can you show examples of custom project settings that you have to configure?

Also I believe no one actually runs npm fund ever.

Run. There will also be a button like this on the npm package page:

[brc-dd]

Then if you often encounter such problems, then it is exclusively a problem of your global vscode config

I don't work on just one project. Every project has different settings. Every project cannot even have the same settings. Sometimes you need to enable deno, sometimes disable formatting, disable prettier and enable eslint or biome, sometimes it's just local cspell suggestions, sometimes you need to enable volar for markdown, sometimes volar errors and you need to disable it. You cannot have single global config or even single fixed project-level config for that.