feat: add output format option with 'gcc'

[vnayar]

Relating to #145, a new command-line option was added. The current output format is named 'default', and a new format 'gcc' was added that uses an error format similar
to gcc, namely: <file>:<lineNo>:<charNo>: <type/severity>: <message>

This command-line option mirrors that used by the common linting tool shellcheck: https://www.mankier.com/1/shellcheck

Example output:

$ ./bin/ec --format=gcc ~/files/dummy.*
../../files/dummy.bat:0:0: error: Wrong line endings or no final newline
../../files/dummy.bat:0:0: error: Not all lines have the correct end of line character
../../files/dummy.d:2:0: error: Line too long (113 instead of 100)
../../files/dummy.d:3:0: error: Wrong amount of left-padding spaces(want multiple of 2)

[vnayar]

I modified the commit description to have the prefix feat:, which I believe is what was causing the build to fail, although I'm not 100% sure. Please approve execution of the workflow.

[vnayar]

Another force-push due to the subject line of the commit being rejected with the following error:

✖   subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case]

I am guessing that capitalizing the letters in the subject will resolve this, but I have no way of checking until the workflow is run.

[vnayar]

I cannot find any documentation regarding the proper case for commit message titles, but all the other examples that are present use lower case. I am making yet another attempt to satisfy this commit linting tool. Please re-run the workflow, because currently only maintainers can do this.

[vnayar]

Updated testfiles/generated-config to include an empty "format" value.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (da7e006) 84.58% compared to head (672dc63) 84.89%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #319      +/-   ##
==========================================
+ Coverage   84.58%   84.89%   +0.31%     
==========================================
  Files           8        8              
  Lines         681      695      +14     
==========================================
+ Hits          576      590      +14     
  Misses         81       81              
  Partials       24       24              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vnayar]

When time permits, please take a look. The option to alter the output format is called "--format" and the first added alternative is "gcc". The output format and commnd-line options are inspired from https://www.shellcheck.net/

[vnayar]

@mstruebing Could you take a moment to look at this PR to add a --format option, with one additional format so far, --format=gcc, which outputs line-oriented output similar to gcc. The option name and value were borrowed from the common linting tool shellcheck.

[mstruebing]

Thank you this is a good PR.
Sorry for taking so long.

[mstruebing]

I've created a new release, 2.8.
Can #145 be closed or does this issue still needs to be open or can it be closed?

[vnayar]

I've created a new release, 2.8. Can #145 be closed or does this issue still needs to be open or can it be closed?

I believe all the described conditions of #145 have been satisfied, namely:

Though the output of editorconfig-checker is human friendly, it is complicated to parse in other tools. A more repetitive one line output format is basic but at least somewhat common. An option to fully print each error per line would be great.