Add a lot more data to info.json

[skullydazed]

Description

This adds a lot of new information to info.json. Besides adding more keyboard metadata we have also added tags! Just add a new top-level key to info.json containing a list of your tags. Example:

{
    "tags": ["tkl", "split"]
}

This also changes the output of qmk info -f text to use dot-notation. This will be handy in the future as we add the ability to query based on JSON information.

Example qmk info -f text output

  skully@zayante:~/qmk_firmware:0$ qmk info -kb clueboard/card -f text
  bootloader: atmel-dfu
  debounce: 20
  diode_direction: ROW2COL
  features.audio: True
  features.backlight: True
  features.bluetooth: False
  features.bootmagic: False
  features.command: True
  features.console: True
  features.extrakey: True
  features.lto: True
  features.midi: False
  features.mousekey: True
  features.nkro: False
  features.rgblight: True
  features.unicode: False
  height: 8
  keyboard_folder: clueboard/card
  keyboard_name: Cluecard
  layout_aliases.LAYOUT: LAYOUT_all
  layouts: LAYOUT_all
  maintainer: skullydazed
  manufacturer: Clueboard
  matrix_pins.cols: F1, F6, F7
  matrix_pins.rows: B4, F0, F4, F5
  platform: unknown
  processor: atmega32u4
  processor_type: avr
  protocol: LUFA
  rgblight.brightness_steps: 17
  rgblight.hue_steps: 10
  rgblight.led_count: 4
  rgblight.pin: E6
  rgblight.saturation_steps: 17
  split.transport.protocol: serial
  usb.device_ver: 0x0001
  usb.pid: 0x2330
  usb.vid: 0xC1ED
  width: 10

Types of Changes

• Core
• Enhancement/optimization

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).

[noroadsleft]

qmk info -h seems to imply qmk info -f defaults to friendly, but this doesn't work in practice:

 noroadsleft  ~/qmk_firmware/keyboards/clueboard/66/rev4  (pr/13366)
$ qmk info -f
usage: qmk.exe info [-h] [-r] [--ascii] [-f FORMAT] [-m] [-l] [-km KEYMAP] [-kb KEYBOARD]
qmk.exe info: error: argument -f/--format: expected one argument

 noroadsleft  ~/qmk_firmware/keyboards/clueboard/66/rev4  (pr/13366)
$ qmk info -h
usage: qmk.exe info [-h] [-r] [--ascii] [-f FORMAT] [-m] [-l] [-km KEYMAP] [-kb KEYBOARD]

optional arguments:
  -h, --help            show this help message and exit
  -r, --rules-mk        Render the parsed values of the keyboard's rules.mk file.
  --ascii               Render layout box drawings in ASCII only.
  -f FORMAT, --format FORMAT
                        Format to display the data in (friendly, text, json) (Default: friendly).
  -m, --matrix          Render the layouts with matrix information.
  -l, --layouts         Render the layouts.
  -km KEYMAP, --keymap KEYMAP
                        Show the layers for a JSON keymap too.
  -kb KEYBOARD, --keyboard KEYBOARD
                        Keyboard to show info for.

Specifying friendly also doesn't seem to do anything:

 noroadsleft  ~/qmk_firmware/keyboards/clueboard/66/rev4  (pr/13366)
$ qmk info -f friendly
Keyboard Name: Clueboard 66% rev4
Manufacturer: Clueboard
Maintainer: skullydazed
Keyboard Folder: clueboard/66/rev4
Layouts: LAYOUT_66_ansi, LAYOUT_66_iso, LAYOUT_all
Size: 16.5 x 5
Processor: STM32F303
Bootloader: stm32-dfu
Layout aliases: KEYMAP=LAYOUT_all, LAYOUT=LAYOUT_all

[skullydazed]

Apologies for missing this last week.

qmk info -h seems to imply qmk info -f defaults to friendly, but this doesn't work in practice:

You have to supply an argument to -f. If you don't supply -f at all it defaults to the friendly output.

Specifying friendly also doesn't seem to do anything:

That's working as designed. If you were to override the default output, EG qmk config info.format=text, then using qmk info -f friendly would look different.

[skullydazed]

Tests are passing now and it can merge clean.

[skullydazed]

I've rebased against develop and fixed a couple new errors that cropped up.