Add prompts for the whole story

[Phoscur]

Following up on #7 and some experiments in oryx-layer-inserter I created #8 with yargs, prompts & node-persist, this covers a base for better UX, adding more commands & caches, as well as merging the repos.

Combined Commandlist:

• auth get JWT authorization token (manual, only possible to automate as user script)
• data get my layouts list
• open new layout revision (manual, TODO automate?)
• insert (create/copy) layer (Copy layers from multiple layouts: Layer Boilerplates #6)
• set-key WIP (Copy layers from multiple layouts: Layer Boilerplates #6)
• wizard create username file, prototype macros Macro Wizard #11
• get* (download-src) keymap source
• process* keymap expanding macros
• compile*
• flash* (manual, TODO Flash Command: Call Wally #12)

*unauthorized mode - auth is actually not needed (only layoutID)

The last three commands and potentially essential parts of the wizard cannot be run inside the browser, but they could also generate a browser snippet to set the macro key, for example. I might explore this later, so the layer-inserter will become a playground for tamper monkey scripts.

Automation as console prompts for Node.JS, initial flow:

0. auth - prompt to get the auth token is a messy manual task, description: localStorage.getItem('jwtToken')
1. data - provides layout & layer IDs (a bit slow for many layouts)
2. open - create a new revision, required if the layout is to be modified (insert, set key) - manual for now
3. wizard - guide through macro creation TODO Macro Wizard #11
4. get (download-src) - get & unzip the keymap source TODO check open
5. process - apply macros expansion, add stuff to the keymap.c file
6. compile - call qmk locally
7. flash - call or at least open Wally (Flash Command: Call Wally #12)

Most interesting "everyday" usage flow

0. auth - needs just to be checked, the token is quite long-lived, if it timed out fall back to caches & prompts in "unauthorized" mode
1. wizard - just skip to change a typo in a macro, or add one from a blueprint... Macro Wizard #11
2. open - don't, just check that no open revision exists, to be ready to download - recognize unchanged
3. download - only if the layout changed
4. process, compile, flash & data - meanwhile processing update caches

I'd like to implement the fast path first: "new but closed revision found" - download & process - no prompts.
How important is this "unauthorized mode"? Likely depends on the usefulness of the wizard (#11) and the potential selection of new macros from a yet-to-be-created macro and layer library... (#6)

What are your thoughts about this?