Add WDL unit tests to CI

[stxue1]

Resolves #5109
Resolves #4941
Also makes the test_giraffe WDL test run with --logDebug so next time it fails similar to here it will give a more detailed answer. I think it is just a networking issues though, as mentioned here.

Also updates the commit to the branch here DataBiosphere/wdl-conformance-tests#46 (one of the arguments wasn't previously working, which that PR fixes.)

Changelog Entry

To be copied to the draft changelog by merger:

• Added WDL unit tests to CI

Reviewer Checklist

• Make sure it is coming from issues/XXXX-fix-the-thing in the Toil repo, or from an external repo.
  • If it is coming from an external repo, make sure to pull it in for CI with:

    contrib/admin/test-pr otheruser theirbranchname issues/XXXX-fix-the-thing
    

  • If there is no associated issue, create one.
• Read through the code changes. Make sure that it doesn't have:
  • Addition of trailing whitespace.
  • New variable or member names in camelCase that want to be in snake_case.
  • New functions without type hints.
  • New functions or classes without informative docstrings.
  • Changes to semantics not reflected in the relevant docstrings.
  • New or changed command line options for Toil workflows that are not reflected in docs/running/{cliOptions,cwl,wdl}.rst
  • New features without tests.
• Comment on the lines of code where problems exist with a review comment. You can shift-click the line numbers in the diff to select multiple lines.
• Finish the review with an overall description of your opinion.

Merger Checklist

• Make sure the PR passes tests.
• Make sure the PR has been reviewed since its last modification. If not, review it.
• Merge with the Github "Squash and merge" feature.
  • If there are multiple authors' commits, add Co-authored-by to give credit to all contributing authors.
• Copy its recommended changelog entry to the Draft Changelog.
• Append the issue number in parentheses to the changelog entry.

[adamnovak]

There are some comments that I think need to be more specific, and it looks like we might not be properly handling failure from one of the test setup scripts.

[adamnovak]

This should fix #4941.

[adamnovak]

It looks like CachingFileStoreTestWithAwsJobStore.testReadCacheMissFileFromJobStoreWithoutCachingReadFile failed because the testing machine lost Internet connectivity to AWS while the test was running.