Output directory

[deeenes]

We should set up a system for management of output directories, probably with the help of pypath-common. The default root should be the current working directory, and we need to come up with a convention of paths within that. It could be something like:

./<networkcommons>/<session-timestamp>/<method>/<network>/...

For example, if we run CARNIVAL and visualize the solutions and plot some quality control, we could end up with something like:

./nc-output/sw74q-20240930-1511/carnival/signor-0/constraints/condition-0.lp
./nc-output/sw74q-20240930-1511/carnival/signor-0/solutions/condition-0.tsv
./nc-output/sw74q-20240930-1511/carnival/signor-0/solutions/condition-0.pdf
...

[Thomas-Rauter]

As a comment to this, I think it would be also a good idea to have a standard handling of filepaths from the technical side, so for example just use the Path objects from the pathlib library (which are cross platform compatible). Because otherwise it will probably be a mix between Path objects and os.paths. And I handle this always like this that both Path objects and os.paths can be specified by the user, but internally, when an os.path is specified, it gets converted to a Path object.