ci: move test-race to its own job

[tac0turtle]

Description

moving test-race to its own job allows us to run it or normal tests on their own. this reduces running jobs. The down side is if they both fail we then have to rerun both of them.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[robert-zaremba]

If we want to optimize it then the better strategy is to avoid duplicated runs:

• run all race tests
• run other tests which were not run with race tests (to not duplicate).

[tac0turtle]

If we want to optimize it then the better strategy is to avoid duplicated runs:

• run all race tests
• run other tests which were not run with race tests (to not duplicate).

I don't get which part of this is not being done. We are running the tests that can't be run in the race detector in tests and the ones that can here. This isn't meant as a speed up. We need to redo the test suite to fix this imo.

[robert-zaremba]

I don't get which part of this is not being done.

The second bullet point. We are duplicate test runs. We will need some smarter script to do it.

[robert-zaremba]

So if this PR won't speed up anything, then what's the improvement?

[tac0turtle]

So if this PR won't speed up anything, then what's the improvement?

moving test-race to its own job allows us to run it or normal tests on their own. this reduces running jobs. The down side is if they both fail we then have to rerun both of them.

as its stated in the description, if normal tests fail there is no need to rerun 10 odd jobs, but only need to rerun 4-5. This reduces the amount of jobs running when rerunning things which unblocks runners for other jobs.

[robert-zaremba]

So, is there a way to re run only one job? I have never seen that option.

I'm not against this PR, so approving, but let's clarify how to use it / take benefit of it.

[robert-zaremba]

I created a task for the optimization I mentioned: #10913