nullbitsco/nibble Configurator rework

[noroadsleft]

Description

Apologies to @jaygreco for not getting around to reviewing #10769. I had actually found issues with the Configurator support a week or so ago, and I put together a fix that I never submitted. (I don't like having a whole bunch of PRs open at the same time.)

I took care to make sure this compiles the same as current master, because all the issues are limited to the Configurator support:

 noroadsleft  ~/qmk_firmware (master)
$ shasum nullbitsco_nibble_*.hex
5cdf805a538f4cd474e8b4d72e126f6c2562d212 *nullbitsco_nibble_default.hex
38eff0623cf95c004337e6b1dd9fccbc17bda79b *nullbitsco_nibble_iso.hex
aea87df4c0ac52d1626ca633e1ae825d405472bf *nullbitsco_nibble_via.hex

...

 noroadsleft  ~/qmk_firmware (cf/nullbitsco_nibble)
$ shasum nullbitsco_nibble_*.hex
5cdf805a538f4cd474e8b4d72e126f6c2562d212 *nullbitsco_nibble_default.hex
38eff0623cf95c004337e6b1dd9fccbc17bda79b *nullbitsco_nibble_iso.hex
aea87df4c0ac52d1626ca633e1ae825d405472bf *nullbitsco_nibble_via.hex

Types of Changes

• Enhancement/optimization
• Keyboard (addition or update)

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• I have read the CONTRIBUTING document.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[jaygreco]

I apologize for the blown-out JSON files. The VS code autoformatter went to town on them and expanded all of the lines in addition to adding tons of whitespace, and I didn't think much of it until seeing the changes in this PR.

[noroadsleft]

I apologize for the blown-out JSON files. The VS code autoformatter went to town on them and expanded all of the lines in addition to adding tons of whitespace, and I didn't think much of it until seeing the changes in this PR.

I actually only format the files this way because they're easier to read/debug like this. I do know they tend to be auto-formatted in a lot of editors. It's not a problem for the API to consume them this way (it doesn't actually care), but if another human needs to read them, I find this way the best, but you have to format it manually. I actually don't use VSCode for largely this reason. (This sort of work is most of what I do in QMK.)