Create Companion v0.4.0

Pinch and spread become inputs of their own, and every input now names how many fingers the
module was flashed for, with each module offering only the counts its firmware really has.

• Pinch and spread are separate inputs. They are the two halves of one field and each
  needs its own key, so the Inputs add row now offers Pinch and Spread on their own and
  no longer offers the combined Pinch & spread: a single key for both halves could not tell
  a pinch from a spread. Two fingers only, on the Tune and on a Touch. An existing combined
  pair keeps working; its two rows are what the separate choices create anyway.
• Both send a run of keys scaled to how far the fingers travel, like a two-finger swipe, so
  those rows carry the One per swipe / Follow swipe switch. One per swipe is the default:
  the gesture fires its action once.
• Finger counts follow the module. The Tune stops at three fingers (it has no 4-finger
  field), so the Inputs page no longer offers 4 fingers for a Tune tap or swipe. A Touch
  still offers 3 and 4 for taps and 2 to 4 for swipes; pinch and spread stay two fingers.
• Every input has a finger count. The any fingers choice is gone: an any-count row next
  to a counted row for the same gesture would fight over the same flashed field and send two
  different things. A row from before finger counts still shows "any fingers" until you pick a
  count; the engine's any-count fallback for bindings is unchanged.

Upgrading: nothing to do. Existing rows keep their keys and counts. If an Inputs row shows
"any fingers" (the default Tune swipes on F17 to F20 are such rows), pick the count that Tune
is flashed for; until then that row cannot be exported as a module profile.

---

Install instructions: https://github.com/traviswye/create-companion/blob/v0.4.0/INSTALL.md