Introduce jobscript exit code check

[leahaeusel]

Description and Context

This is an alternative implementation of merge request !786 on GitLab that improves the error handling in our jobscript driver. This new implementation introduces a flag to the JobscriptDriver that determines whether to raise an error if the jobscript returns a non-zero exit code.

This new implementation does not introduce a second constructor and, therefore, does not break the input-file-based workflow.

In addition, the new error handling allows for catching OSErrors which used to occur when the jobscript_template string was too long.

Related Issues and Merge Requests

• Closes Long Jobscript Template String Not Possible #69
• Blocks
• Is blocked by
• Follows
• Precedes
• Related to
• Part of
• Composed of

How Has This Been Tested?

Checklist

• My commit messages mention the appropriate issue numbers (advised but optional).
• I mention the appropriate issue numbers in this MR.
• I updated documentation where necessary.
• I updated the README where necessary
• I have added as (few,) small and fast tests as possible to cover my changes.

Additional Information

Interested Parties

Possible reviewers:

Other interested parties:

[gilrrei]

Thanks, @leahaeusel, for the addition; I think this is an important one! Also nice that you added loads of tests.

[gilrrei]

Closes #69