qa: Enforce JSON linter for GCT configs

[thrasher-]

PR Description

Adds a new GHA and Makefile utility command to enforce JSON format standards for our configs using jq. Also sorts the exchanges by name for now rather than the whole file for starters.

Type of change

• New feature (non-breaking change which adds functionality)

How has this been tested

• go test ./... -race
• golangci-lint run
• GHA
• make lint_configs and manual breaking to make sure the diff wigs out

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation and regenerated documentation via the documentation tool
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally and on Github Actions with my changes
• Any dependent changes have been merged and published in downstream modules

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.03%. Comparing base (44d50a3) to head (cfecfd7).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1526      +/-   ##
==========================================
+ Coverage   36.02%   36.03%   +0.01%     
==========================================
  Files         411      411              
  Lines      176891   176914      +23     
==========================================
+ Hits        63726    63757      +31     
+ Misses     105384   105369      -15     
- Partials     7781     7788       +7     

see 25 files with indirect coverage changes

[shazbert]

Tickity Tack.

[shazbert]

Suggestion: might be able to use files=$(git ls-files '*.json') so we can conform everything and for future files and filter by config key word. But that seems like a pain. So only a suggestion.

here's the output:

[thrasher-]

Yep, it was made to be extensible but this PR only targets our mainly touched configs for now

[gloriousCode]

tACK!

make lint_configs
Checking if jq is installed...
Processing config_example.json...
jq: parse error: Invalid numeric literal at line 16, column 0
jq processing failed on *.json
make: *** [lint_configs] Error 1

make lint_configs
Checking if jq is installed...
Processing config_example.json...
Processing testdata/configtest.json...

Confirmed that it works 🌞 Emoji's inside yml files is approved too

[gloriousCode]

retACK! Increase in actual human friendliness detected

make lint_configs
-n Checking if jq is installed... 
OK
-n Processing config_example.json... 
OK
-n Processing testdata/configtest.json... 
OK

make lint_configs
-n Checking if jq is installed... 
OK
-n Processing config_example.json... 
OK
-n Processing testdata/configtest.json... 
jq: parse error: Invalid numeric literal at line 462, column 0
FAILED
make: *** [lint_configs] Error 1

[shazbert]

ch tack

[gloriousCode]

make lint_configs
Checking if jq is installed... OK
Processing config_example.json... OK
Processing testdata/configtest.json... OK

make lint_configs
Checking if jq is installed... OK
Processing config_example.json... OK
Processing testdata/configtest.json... jq: parse error: Invalid numeric literal at line 462, column 0
FAILED
make: *** [lint_configs] Error 1

Now with less -n