Improve macro edit form UX and styling

[mickmister]

At the moment, the experience of configuring midi macros is clunky and unintuitive. The task here is to readjust the UI styling and possibly rethink the UX flow of setting up and using macros.

UI components related to configuring macros are all defined throughout the files in this folder. Essentially any.tsx file there
https://github.com/jamtools/jamtools/tree/main/packages/jamtools/core/modules/macro_module/macro_handlers

Any existing styling done in those components is done through style attributes, partially due to previous lack of support for including css in the webapp bundle.

---

All macros instantiated by all modules are currently shown on the centralized page http://localhost:1337/modules/macro. Specifically that page renders all edit components for all created macros.

Modules can also display these on their own pages via accessing the given macro's exported edit and show components like so:

https://github.com/jamtools/jamtools/blob/30aba0e40d489d30ad2d11d1ad8afcc98da9fd75/packages/jamtools/features/modules/dashboards/keytar_and_foot_dashboard/single_octave_root_mode_supervisor.tsx#L276-L279

The eventual plan is to have the components for these macros shown on the module's page itself, without the module needing to manually render those. The framework will take care of organizing those instead. This will be more relevant when the snack system is implemented. This piece is out of scope for this task, though just explaining this for context of where these components will eventually be shown automatically.

---

The task here is to:

• Try out configuring a macro as a user
• Take note of the clunky process
• Consider and discuss any functional improvements
• Consider and discuss any styling improvements

After discussing this, we can decide the desired result and determine what code needs to change

[mickmister]

I've added some more docs including some information on macros here https://docs.jam.tools/jamtools/macro-module

I also added to the project README how to start up the application for development https://github.com/jamtools/jamtools#development

[mickmister]

The thing to be designed here is really more "the UX of interacting with midi instruments in general" Do we want to display the known inputs when assigning a control? At the moment, the way macros work assumes any midi input on your computer can be associated with any feature. Should there be a global spot to enable/disable certain instruments?

The current behavior is a smooth experience, as far as the complications of interacting with midi instruments. The user doesn't need to type in or select their midi instrument name, for example. They just do some action, and it's captured and saved for the feature to use. A macro can capture unlimited mapped inputs from different instruments, so it remembers every mapping that you've had mapped to that feature.

In terms of wanting a global midi configuration, the main things that have come up for me as a user is I want to be able to exclude some midi instruments. Like in some case I want to allow an IAC device's input but not its output, and another IAC device's output but not its input. So in the global configuration I would want to put them in a list of "ignore" device configurations. I like the "all included by default" aspect of the current situation, so I think we just need to add a “exclude input/output for specific instruments” global config. This is a different feature than this issue though, but it’s kind of related.