Modularize app

[tsostarics]

Commit 03d5927 introduces a module to handle all the color management for the plot, along with the colour picker inputs. With this under my belt I think i can start modularizing the application, which should make it a lot easier to maintain moving forward. A few things off the top of my head that could be turned into modules include the buttons below the plot, the loadfile button, and the tools sidebar. I think this will make it easier to omit specific functionality from the eventual web app as well.

[tsostarics]

Update on this, the following modules now exist:

• praat_module: Handles all the inputs to forming the praat commands (audio directory, etc) as well as the button UI and server code and the glueQuestion sweetalert tip
• color_module: Handles the colors for the plot, namely the three colour picker inputs and the theme that tracks light/dark mode
• window_resize_module: Kind of a weird one, tracks whether the window size changes and adjusts the plot size accordingly. Uses a heuristic with the sole goal of avoiding the case where the plot is too big after making a window smaller. Might put it back into the main app file later on since it has a quirk where the windowChange input is actually visible to the main server, and so has to be passed INTO the module server instead of it just being available like normal.
• annotation_module: Manages the notepad and badge inputs along with providing reactives to save and update the values with file navigation.

I'll probably move the diagnostics into their own module as well. A lot of the remaining things are either too small to bother moving them out or are really big and depend on multiple inputs, so it'll be a big push to modularize it. In the latter case it'll be worth the trouble, but it'll just take some time to work with so it might need to come after the proceedings is written.

[tsostarics]

Returning to this again, I'll be working on modularizing the following before implementing #58 :

• [x] module_loadfile: The load file button has a lot of parts to it, so I'm moving this to its own module to clean things up a bit.
• [x] module_octaveshift: The double and halving pulses are largely the same, so it would be easier to move this to a separate file. The undo transformation implementation will also be held in this module. The halvePulses and doublePulses reactives need to be exported so they can be passed to the shortcut keys. The pitch range input also needs to be passed tot his.
• [x] module_diagnostics: will hold the diagnostic information and refreshProgressButton UI component

[tsostarics]

the shinyJS handling with the dynamic UI dropdown components for the edited and unedited file selection boxes was annoying to debug so I'm going to leave those components as is, but otherwise the three modules are now available

[tsostarics]

I edited the plotting code a bit in 2dd94d0 so that the parts of the plot that don't change very frequently (colors, theme, etc) are offloaded to a reactive so the ggproto objects can be reused more easily instead of recreating them every time the plot renders. The code is a bit more readable and modular as a result, and could be moved to a separate module somewhat more easily now. There will be a lot of inputs passed to it though, but it will make it easier for me to edit the web app when i get around to it again.