feat: timeouts

[tristan-f-r]

Adds timeout to algorithms as a demonstration of passing through errors. Closes #316.

Caveats:

• This does not work with singularity (singularity has no docker wait equivalent and to implement timeouts in singularity would probably require constant polling of a detached thread)
• ML requires at least one pathway, and failing pathways can break ML-work. How do we want to handle downstream analysis when errors occur (including in the future heuristic errors?)

[read-the-docs-community]

Documentation build overview

📚 spras | 🛠️ Build #31218767 | 📁 Comparing c2febff against latest (18f2cf8)

🔍 Preview build

Show files changed (3 files in total): 📝 3 modified | ➕ 0 added | ➖ 0 deleted

File	Status
genindex.html	📝 modified
fordevs/modules.html	📝 modified
fordevs/spras.html	📝 modified

[ntalluri]

This does not work with singularity (singularity has no docker wait equivalent and to implement timeouts in singularity would probably require constant polling of a detached thread)

This is a problem; if this is something we are going to use for the benchmarking study we need this to work with singularity because CHTC only uses singularity/apptainer.

[tristan-f-r]

I originally assumed this was a more esoteric PR to test the error-handling workflow. Though, based on the meeting just now, I'll look into a nice way to get this working with Singularity.