Add Code Standrads through .editorconfig

[petrspelos]

Summary

Added a .editorconfig file with specific rules for .NET and C#. Some of these rules are fairly strict and will require either softening through setting the severity to suggestion or deletion altogether.

@ maintainers, feel free to commit changed into this PR.

We should hopefully see the warnings introduced in the CI/CD pipeline, if not, feel free to checkout and build the branch. By default, these warnings should show in your Visual Studio Output window (or CLI for the first build). Some are suggestions and will be only visible in the appropriate files through the IDE.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] Refactoring (non-breaking change to code and structure)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Notes

The .editorconfig should be annotated, so feel free to search for a specific warning by what it actually says. You can also search by the Code (ie. CA1716)

Co-assigning @PlesnikJakub since we discussed some of these changes together. ☺️

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[petrspelos]

I've also noticed some of these diagnostic warnings are only showing in IDEs, so be mindful of that. 👍 🙌

[TomasNiemczyk98]

Looks good to me, also this could probably also be included in the Web API template @PlesnikJakub ?

[petrspelos]

Looks good to me, also this could probably also be included in the Web API template @PlesnikJakub ?

+1, though of course changed according to your preferences