Rolling submission

[rvhonorato]

This PR leverages go's concurrency with a semaphore pattern to control the flow of job submissions. It adds a job.WaitUntil method that runs j.UpdateStatus to pass the status up and move to the execution of a next job.

In summary its a "rolling-submission" approach, that new jobs are submitted as soon as the old ones match the expected status. This is controlled by the max_concurrent parameter.

One important note here is that the SLURM status and the haddock-runner status are not the same! The j.UpdateStatus method handles this translation.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00%	✅ 100.00%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (87ca2d9)	1213	1213	100.00%
Head commit (8fe8aab)	1323 (+110)	1323 (+110)	100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#100)	115	115	100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{You may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation}