Settings - Fixes for whitespaces and comments, added unit tests

[johnb432]

When merged this pull request will:

• Title. More specifically it should address Latest CBA version does not honor white space in the CBA settings Configuration File for Task Force Arrowhead Radio (BETA) #1619 and Some CBA Settings fail to import #1620.
• Comments fix: From line 29 through 34.
  • If the order of the regexReplace commands is switched (so removing multiline comments first, then single line), it will not work. This makes be believe both my regex' are not robust enough.
  • There are cases I have thought of that could be problematic, but I'm not sure how to test, because the .editorconfig file restricts them. E.g. having a single line comment be at the end of a file, but not having a newline (is that even possible?) or using different newline encoding styles (LF, CR and CRLF).
• Whitespace fix: Removal of lines 25 through 29. The comment was mostly wrong, except in one instance:

If in single quotes, it removed the whitespaces (this is the old code):
' T E S T ' becomes "TEST"

Single quoted strings will be converted into double quoted strings.
So ' T E S T ' will remain/become " T E S T ".

• More info can be found here: https://discord.com/channels/976165959041679380/976228110078992456/1164706891952300152 (CBA discord, a thread I made concerning the findings relating to whitespace problem).

I'd appreciate any help.

[jonpas]

Tabs!

[johnb432]

Tabs!

Tabs inside or outside of the strings? I saw the github action complained about tabs, but I want the tests to run with tabs (to make sure they work - unless that's unnecessary?).

[jonpas]

Oh right, I see now. @PabstMirror do we have a way to ignore validating parts of code?

I don't think we need to test for tabs though, as whitespace is whitespace to Arma, but I may be wrong.

[PabstMirror]

passing CI now

[johnb432]

Something I forgot to mention explicitly for the whitespace fix regarding single quoted strings:
They will no longer have their whitespace removed. Plus, they will be converted into double quoted strings.
So ' T E S T ' will remain/become " T E S T ".

I'm going to re-test it though, to be 100 % certain, as the tests above were affected with Advanced Developer Tools. Confirmed.