Remove trim_whitespaces from editorconfig

[Youssef1313]

See dotnet/sdk#12865 (comment)

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @ViktorHofer
See info in area-owners.md if you want to be subscribed.

[jkotas]

Did you find this option problematic in dotnet/runtime repo?

I have not run into any of the issues mentioned in the linked comment while working in dotnet/runtime.

[jkotas]

Maybe there are a few files where it may be causing problem, but I would think that the benefits outweighs it.

[stephentoub]

I don't understand why we're removing this. It's very helpful.

[Youssef1313]

@stephentoub @jkotas Thanks for reviews. But as stated in sharwell's comment:

Some files have significant trailing whitespace (e.g. Markdown, C# verbatim string literals)

I think if, now there aren't significant trailing whitespaces, I think it's not guaranteed that this will remain the same in future.

[stephentoub]

We have an analyzer that fails the build if there's trailing whitespace in C# files.

And end-of-line literally invisible code is practically impossible to maintain.

Please point to an actual example in dotnet/runtime where it's causing a problem.

[Youssef1313]

@stephentoub Thanks for clarifying that. In that case, it would be possibly to exclude this option for markdown only? (I haven't seen an example in this repo where markdown trailing spaces are significant, but I've seen that in dotnet/docs before).

Also, can I ask which analyzer is used for the trailing whitespaces in C# files?

[Youssef1313]

@stephentoub Another solution for the markdown files is to enable markdownlint with MD009 rule enabled.