Add output and labels to quickcmd

[pajawojciech]

Changes

• Custom names for commands, editable via Shift+N
• When name is not empty then it shows instead of command
• Checkbox to display command output in a popup window (Shift+O)
• Config data is stored in separate config file because data structure changed from string array to objects array (in quickcmd-v2.json instead of quickcmd.json)
• If there is no data in new config file then auto migrate from old config

quickcmd window:

Output window:

Old and new settings file:

Issues

• Feature Request: Ability to name or label saved commands in quickcmd dfhack#3420
• show output of commands run via gui/quickcmd dfhack#4998

[chdoc]

@ab9rf Is there a policy for updating the configuration format for tools that are not world or site specific? I would tend to keep the configuration filename aligned with the name of the tool without adding any version suffixes, putting any versioning information about the configuration file format into the configuration file itself. That is, back up the old configuration file under a new name and then convert the configuration in place.

[ab9rf]

I'm inclined to agree with you here: keep the file name the same and store the version information into the file itself.