Json formatting and reorder

[Cipulot]

Description

This PR aims to align the formatting and key order of the JSON merged in the repository.

The formatting of the JSON follows the following rules:

• indent_style = space
• indent_size = 2
• end_of_line = lf
• charset = utf-8
• trim_trailing_whitespace = true
• insert_final_newline = true

These rules, in combination with the default formatter for JSON files found in VSCode and similar apps, introduce additional line usage, in cases like the following:

While this might reduce the final readability, it's far easier to have the auto-formatted as the base approved layout, rather than count on the auto-formatted to be modified again to have 1 liner again.

The key has been consolidated as follows:

• "name",
• "vendorId"
• "productId"
• "firmwareVersion"
• "matrix"
  • "rows"
  • "cols"
• "customFeatures"
• "customKeycodes"
• "keycodes"
• "menus"
• "lighting" (for src boards)
• "layouts"
  • "labels"
  • "presets"
  • "keymaps"

This order allows for a better flow of information, as well as aligning all the JSON already merged in the repository to follow the same order. This order is the preferred and requested from now onwards, change the documentation to indicate the preferred order will be done after this PR.

Subsequently, the PR checklist will receive additional checks for code formatting and key order.

[syrah94]

hello xelus22 and cipulot, this is Syrah from qwertykeys, we have been following a keyboard firmware developing team and their progresses - and we'd want to bring some of the feature they developed into qmk/via so we'd love to know how should we do this? is there a process for one to "become" the code reviewer? we wish to do our part to contribute and return to the community but I am not sure where to send the message! please let me know the best way to reach out if this is disturbing 🙏

[Cipulot]

Hello there @syrah94 .
In case of addition suggestions, the usual policy is to open an Issue or a PR draft and use that as a discussion platform.
From what I can gasp from your message that would probably have to target the VIA App, and not the keyboards repo.

In any case you can reach us through the VIA discord server and from there through DMs in case you need to.
Here is the VIA discord server link: https://discord.gg/nJZ8Vy7s