Refactor bootstrax

[JoranAngevaare]

Bootstrax has become a huge script with many nuts and bolts that could do with some refactoring for readability. Since I am not leaving any time soon, this issue can stay open for a while to collect some ideas (feel free to add).

Classes (add the following as objects in bootstrax):

name	current # lines	Envisaged usage
Process	500 lines	For a given run, do run strax multiprocessing
Target	120 lines	Given a rundoc, infer which target we should be using (perhaps join with Resources/compression class)
Resources/compression	150 lines	Given a rundoc, figure out what cores, max-messages and raw-record compressor can be used for this run
Database class	?500 lines?	Communicate with the RunDB/DAQDB about the run, files, host etc.
Logging class	..	just use the daq-logger
Host class	300 lines	monitor data and state of the host
Config handler	~150 lines	Put the configs in a seperate file

Documentation:

• On the website ~80 lines

Functionality:

• Smarter shutdown/restart

[JoranAngevaare]

Also include XENONnT/utilix#51

[JoranAngevaare]

fail when a post-process target is not in the context