Catch sbatch errors in CLI commands

Whenever sbatch exits with an error, the error is just passed to the .err log for the invoking job, but the job is marked as COMPLETED in the sacct log. This makes it difficult to determine how much data was not processed because the jobs just weren't submitted at all. This MR wraps the subprocess.run calls for sbatch in try-except blocks that pass any stderr messages back from the subprocess to the invoking command and raises an exception instead of exiting normally. This will mark those jobs as FAILED in the sacct database instead of COMPLETED.

added 2 commits

• efa87ebd - add conditional to remove any passed timedelta values less than or equal to 0
• 25f06a51 - Merge branch 'bugfix-remove-0-from-timedelta-vals' into bugfix-catch-slurm-fail-to-submit-errors

Compare with previous version

added 3 commits

• 8f7e49d8 - 1 commit from branch rc:patch-v0.5.1
• 1553fc8a - add try-except around sbatch to capture any potential errors during child job submission
• 2687ed8f - change to raise error instead of just printing message and exiting normally

Compare with previous version

merged