Fix up Info.Json files that weren't parsing correctly

[ToastyStoemp]

Description

There were a few boards that still had comments, missing comma's or extra comma's that wouldn't parse.
This fixes those boards

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

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.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[zvecr]

info.json is still hjson at the moment, however the .json extension is maintained for the amount of impact renaming would currently have. We currently have not made a decision on if we will downgrade to json any time soon.

Apart from keyboards/kbdfans/kbdpad/mk3/info.json, the files were missed on purpose in the previous refactoring pass.

[fauxpark]

Comments are allowed in info.json; they are actually meant to be HJSON. The QMK API serves these as proper JSON: https://keyboards.qmk.fm/v1/keyboards/handwired/jscotto/scotto36/info.json

[ToastyStoemp]

I scanned through all current boards in develop, these were the only boards that didn't parse. Hence I was convinced it was pretty much supposed to be json, I can revert the comment changes and just keep the small comma fixes