pipelines can hang if job stuck queueing for too long with no nodes available

[andrew-m-leonard]

Consider having a timeout for waiting for a node when "none" are available. Distinguish this to none available, due to them all being busy, so none here means "none at all"

[adamfarley]

I agree. Perhaps the job status could be "aborted" due to timeout, and "failed" if no nodes exist?