modularize startup/setup sequence

[adcxyz]

for personalizing nUFO setups, and for including nufo into larger setups, it would be useful to have a separation of setup stages, so it is easy to run non-default nufo setup code in between them. This is already sketched in the example startup file, but could use more discussion, to arrive at recommendable best practice patterns for modular SC project setups in general.

[adcxyz]

Two major use cases for NTMI:

1. Standalone mode with user-defined setup modification This has been the assumed mode for NTMI code so far.

2. Integration of NTMI or parts of it in a larger setup.

For this use, these parts in NTMI should be separable:

• Server: ** setup only when not booted, else assume fine and skip
• Processes & Presets set numIns, numOuts specifically for NTMI processes liveInput: set chan numbers of ins?
• Interfaces: defaults to always load optionals to load only when prefs say so, or dynamically by hand
• GUI: only if q.hasGui, specify which mainGui in prefs, or decide by isPi, screenSize?
• MainFX: ** should be optional or at least skippable

[adcxyz]

Butz setup is also global, should be modifiable ...

[adcxyz]

with recent commits NTMI has become much easier to load together with other projects: most of its functions are now in NTMI.q, and setup stages are easy to configure.