Add cli command to import keyboard|keymap|kbfirmware

[zvecr]

Description

Mostly as im too lazy to copy stuff into the tree manually.

Extended the import commands to also provide a CLI equivalent of https://noroadsleft.github.io/kbf_qmk_converter/.
Basic support right now, on which can be iterated in future develop cycles. I also have an in progress replacement for kbfirmware, which will rely on the import command rather than provide hosted compilation.

Examples

qmk import-keymap ~/Downloads/asdf2.json 
Ψ Importing asdf2.json.

Ψ Imported a new keymap named asdf2.
Ψ To start working on things, `cd` into keyboards/takashicompany/dogtag/keymaps/asdf2,
Ψ or open the directory in your preferred text editor.
Ψ And build with qmk compile -kb takashicompany/dogtag -km asdf2.

qmk import-kbfirmware ~/Downloads/gh60.json
Ψ Importing gh60.json.

⚠ Support here is basic - Consider using 'qmk new-keyboard' instead
Ψ Imported a new keyboard named gh62.
Ψ To start working on things, `cd` into keyboards/gh62,
Ψ or open the directory in your preferred text editor.
Ψ And build with qmk compile -kb gh62 -km default.

qmk info -l -kb gh62
Keyboard Name: gh62
Manufacturer: TODO
Maintainer: TODO
Keyboard Folder: gh62
Layouts: LAYOUT
Processor: atmega32u4
Bootloader: atmel-dfu
Layout Layout:
┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐
│  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  │
└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘
┌────┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌────┐
│    ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││    │
└────┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└────┘
┌─────┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌───────┐
│     ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││       │
└─────┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└───────┘
┌───────┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌──┐┌─────┐┌──┐
│       ││  ││  ││  ││  ││  ││  ││  ││  ││  ││  ││     ││  │
└───────┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└──┘└─────┘└──┘
┌───┐┌───┐┌───┐┌───────────────────────┐┌───┐┌───┐┌───┐┌───┐
│   ││   ││   ││                       ││   ││   ││   ││   │
└───┘└───┘└───┘└───────────────────────┘└───┘└───┘└───┘└───┘

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

[drashna]

Conceptually, looks sound, and it looks like the python doesn't break anything.