Run pytest before ruff linter checks

[jordandsullivan]

I want to test the functionality of a change before checking the formatting. In this way you get a failure like on an unused import before the code itself runs: https://github.com/unitaryfund/ucc/actions/runs/13554895918/job/37886926715

[bachase]

LGTM.

In addition, if you hadn't already, you could consider:

1. Depending on your IDE, you may be able to set the ruff format and ruff linter to run automatically whenever you save a file.
2. You can enable pre-commit hooks (mentioned in our docs here) that will automatically format and fix any linter issues right before any calls to git commit complete (or will prevent commit if it would cause a conflict). The benefit there is it catches it earlier, and avoids an extra commit for fixing.

cc @natestemen and @Misty-W if they have any different workflows. We can consider documenting this more in the docs or README as well.

[natestemen]

Okay by me. Another way to achieve this is to use continue-on-error, so both the tests, and the linting can run. It does look like there is some uncertainty on the behavior of this flag from stackoverflow, but we could test it!

[jordandsullivan]

I would rather just stick with the order for now rather than test a new flag. I will update my pre-commit hooks though thanks!