Prevent certain tests from being run twice in CI

[stxue1]

This fixes #4521. Only the batch_systems, jobstore_and_provisioning, and wdl tests are affected, as I think the integration tests and py310_main benefit from running all their current tests.

Changelog Entry

To be copied to the draft changelog by merger:

• Prevent certain tests from being run twice in 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]

@stxue1 it looks like this is on top of 802dd1c when it should have been on top of d686dac which is the squashed-and-merged version of the commit. You probably didn't to a git fetch origin && git checkout origin/master (assuming origin is your remote for this repo) before starting your work.

We don't want to merge this like it is, because then we'll be squashing in a bunch of duplicate copies of the commits from your last PR.

I think what you want to do is:

1. git fetch origin
2. git rebase -i origin/master
3. Delete the lines for all the commits that were in your last PR (so revert accidental rename and everything before that) and save the file, and close the editor, so rebase can re-make all your commits that are for this feature on top of the current master branch.
4. Force push the result to this PR's branch.

[adamnovak]

I think it needs rebasing, but the code looks right.

[adamnovak]

Shouldn't cutting this be part of #4530 and not this PR?

I guess it's fine to do it here though.