pipeline_job.sh submission scripts are outdated

[Nicolai-vKuegelgen]

Is your feature request related to a problem? Please describe.

The current pipeline_job.sh submission scripts are the main/best-practice entry point into running snappy steps. However, they are relatively old and some key assumptions do not hold up anymore:

• It is assumed that any existing conda installation is named "miniconda3". This can not be assumed anymore, especially due to miniconda entanglement with the now problematic defaults channel. Also BIH HPC recommendation is now to use miniforge.
• If one maintains multiple conda installations (i.e. to fully separate snappy production environments), the current scripts may NOT default to the active miniforge/conda executable but another one.

Describe the solution you'd like

The pipeline_job.sh scripts should:

• always default to an active/loaded conda executable (i.e. by checking if $CONDA_EXE is set)
• have at least the option of looking for miniforge instead of miniconda3 folders

Additionally it would be nice if snappy could add support for conda's --conda-prefix flag, to allow user/system wide installation of conda environments instead of re-doing all environments inside each snappy project.