Make certain tests sequential to prevent conflicts

[andystaples]

Makes a subset of the E2E tests run sequentially after the rest to prevent conflicts (unexpected purge results, unexpected running orchestrations)

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation PR is ready to merge and referenced in pending_docs.md
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• I have added all required tests (Unit tests, E2E tests)
• My changes do not require any extra work to be leveraged by OutOfProc SDKs
  • Otherwise: That work is being tracked here: #issue_or_pr_in_each_sdk
• My changes do not change the version of the WebJobs.Extensions.DurableTask package
  • Otherwise: major or minor version updates are reflected in /src/Worker.Extensions.DurableTask/AssemblyInfo.cs
• My changes do not add EventIds to our EventSource logs
  • Otherwise: Ensure the EventIds are within the supported range in our existing Windows infrastructure. You may validate this with a deployed app's telemetry. You may also extend the range by completing a PR such as this one.
• My changes should be added to v2.x branch.
  • Otherwise: This change applies exclusively to WebJobs.Extensions.DurableTask v3.x. It will be retained only in the dev and main branches and will not be merged into the v2.x branch.

[nytian]

Thanks for the PR! Left a small questions:)

[nytian]

Just to confirm -- this attribute ensures the test runs after the other tests?

[andystaples]

Correct - per XUnit documentation, tests that are part of a collection initialized with the parameter DisableParallelization = true will run after all parallelized collections. Each test in these collections will be run independently.
Testing locally, I saw our current suite complete approx. 20s slower with this change - something to keep in mind when writing new tests is only mark them sequential if it is necessary.