Adding EditorConfig and spelling_exclusion.dic

[frobijn]

Description

This commit contains the final versions of .editorConfig and spelling_exclusion.dic as discussed in #134.

Motivation and Context

See discussion in #tools in Discord. The .editorconfig file is the only supported way (by Microsoft) to add repository-specific settings that control the behavior of the Visual Studio editor - as an alternative to changing the global Visual Studio settings. It is the only way to configure the spell checker.

How Has This Been Tested?

• Spell checked all C# source code in this repository.
• Added a space to every C# source file from every project and saved it with auto-formatting on. According to git, the resulting file was unchanged.

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[josesimoes]

LGTM!