Initial support for auto-starting apps.

BREAKING CHANGES The configuration file has been simplified.

Old syntax:

"Apps": [
  {
    "Name": "Terminal",
    "HotKeys": [ { "Modifiers": "Control", "Key": "D1" } ],
    "FindExisting": {
      "ProcessName": "WindowsTerminal"
    },
    "StartNew": {
      "FileName": "wt"
    }
  }
]

The "ProcessName"-property is optional for processes where they are the same.

New syntax:

"Apps": [
  {
    "Name": "Terminal",
    "HotKeys": [{ "Modifiers": "Control", "Key": "D1" }],
    "FileName": "wt",
    "ProcessName": "WindowsTerminal"
  }
]

Auto-starting apps to toggle

Currently exploring the direction where an app has an "AttachMode", which dictates how WTQ grabs an app:

• FindOrStart (default) Looks for an existing process as specified by the "FileName"- and/or "ProcessName"-properties. If no process was found, a new one will be started using the value under the "FileName"-property.
• Find Just looks for existing processes as specified by the "FileName"- and/or "ProcessName"-properties. No new processes will be started (previous version behavior, where you always had to manually start the app.
• Start (very experimental) Always starts a new process, specifically to be used by WTQ. Meant for apps that have multiple open instances. Initially meant for (among other things) browsers, but these turn out to be more complicated. This will be documented later.
• Manual Attaches whatever app has focus, when the hot key is pressed. Keeps the app attached until WTQ is closed.

The mode can be specified per app (note that "FindOrStart" is the default:

"Apps": [
  {
    "Name": "Terminal",
    "AttachMode": "Find", // Only attach to process that is already running, don't auto-start one.
    "HotKeys": [{ "Modifiers": "Control", "Key": "D1" }],
    "FileName": "wt",
    "ProcessName": "WindowsTerminal"
  }
]