ci: drop pytest in favor of Sprocket test

[a-frantz]

This PR is for demonstration purposes of the RFC document here

this PR has morphed from a demonstration into a real PR for swapping our test infra from pytest to Sprocket. Still a WIP as not all the tests are written yet and it has not been hooked into CI yet

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[a-frantz]

all tests passing 🎉
@adthrasher for local testing, I picard::mark_duplicates uses more memory than available on my MPB, so I've annotated that test with high_mem. Running sprocket dev test -f high_mem at the root of this branch should be all green. I'm seeing all green on the cluster as well. For executing tests there, try a parallelism = 300 to get a good balance of speed and resource utilization. See stjude-rust-labs/sprocket#821 for why just lifting the parallelism throttle completely doesn't work

[adthrasher]

I don't recall what this parameter does. Why are we removing the argument?

[adthrasher]

Note to self: GATK4 tests work locally