Iterate over sessions

[CodyCBakerPhD]

The most important feature we probably need at this point is automated iteration over a parent folder of multiple sessions; some experiments have hundreds of sessions, so it is totally unfeasible to ask people to repeat our convenient process that many times

We've been discussing this largely in Figma so far, which we probably still should as the mockups become more detailed, but opening this issue to keep official track of priorities

Also probably going to intimately entangle development of this feature on the GUIDE with this feature branch of NeuroConv (#377)

[garrettmflynn]

Here's an updated list of all the required behaviors the Session Manager will need to link into other GUIDE features appropriately:

• Render sub-properties of the JSONSchemaForm as accordions (rather than Split JSON Schema across Generated Pages #122)
• Add a Preview button to allow users to preview a single session at any time
  • On the next page, select a random session and generate the preview for explicit confirmation
  • This has led to storing a new paths.config.json file in the base of the project, in case we need to refer to a file across Python and JS. Currently, this is loaded globally when the server starts—though there may be a more pythonic way to do this
• Add an indicator on the sidebar for whether a single session's requirements are met
• Render manager-level notifications (e.g. "x sessions are not valid") before individual session notifications ("session x has y problems")
  • Removed the warning popup since this would run for each form.
  • Now we are validating each session one-at-a-time, so only the first invalid session will throw an error. The status indicators otherwise tell users whether other sessions are valid or not.
• When adding a new interface, ensure old user-specified metadata is maintained + merged rather than overwritten.

[CodyCBakerPhD]

Done after a series of PRs