Added vscode config to fix bogus protoc compiler import errors

[cmaglie]

Please check if the PR fulfills these requirements

See how to contribute

• The PR has no duplicates (please search among the Pull Requests
  before creating one)
• The PR follows
  our contributing guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• UPGRADING.md has been updated with a migration guide (for breaking changes)
• configuration.schema.json updated if new parameters are added.

What kind of change does this PR introduce?

Adds a config file for vscode to fix bogus compiler import errors.

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change, and is titled accordingly?

Other information

[alessio-perugini]

I'm not a vscode user, so my opinion on this sticks with my general preference to be editor agnostic. If we want to remain agnostic, I'd create a doc that can give some tips on how to make some functions work for some IDE.

[cmaglie]

I see, I'll keep the gitignore and see how it goes, my config should stay there without any drawback.