Configure job timeout properly

[Eoghan-Perkins]

Currently the algorithm will run for 6 minutes straight and then time out. This might not be enough time for "historical" jobs that have a couple hour long timebox to process. Should probably offer a dynamic timeout that is 6 minutes for "now" jobs, but if certain time parameters are passed in, a linearly interpolated timeout will be produced and passed to the algorithm runner, taking the duration of the timebox as a parameter.

[Williamj48]

I'd like to work on this, but due to the discrepancies in hardware between my own machine and whatever the FS will have, I am not going to. I think that it is best for the next devs with more information to work with this.