Make VsCode and EditorConfig best friends again

[nulltoken]

Pull request description

.editorconfig setting states that it's ok to have trailing whitespaces in markdown files (although I'm not sure to understand the reasoning behind this 😉).

This VsCode setting prevents it from short circuiting the editorconfig extension when it's installed.

Related:

• trim_trailing_whitespace = false not working editorconfig/editorconfig-vscode#153
• Temporarily Set Configuration For Save Operation microsoft/vscode#65663

Note:
This doesn't add any kind of value to the lib itself.
But as I use both VStudio and VSCode (depending on the kind of change), I eventually got tired all of the useless diff noise when staging changes.

PR meta checklist

• Pull request is targeted at main branch for code
• Pull request is linked to all related issues, if any.

Code PR specific checklist

• My code follows the code style of this project and AspNetCore coding guidelines.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• I have updated the appropriate sub section in the CHANGELOG.md.
• I have added, updated or removed tests to according to my changes.
  • All tests passed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

see 1 file with indirect coverage changes

[linkdotnet]

Hmmm. The root editorconfig can’t handle that? In the *.md section of the file?

[nulltoken]

Hmmm. The root editorconfig can’t handle that? In the *.md section of the file?

It looks like it doesn't. My understanding is that VSCode triggers its own trimming before the EditorConfig extension can chime in to prevent it. See the related issues in the description.

[linkdotnet]

Ahh, thanks for clarifying. I just skimmed through the issue - if that is the case: Go, go, go for the merge button and big thanks!