Run Playwright and dotnet tests in parallel in CI

[rmunn]

Fixes #831.

I haven't removed the "Run Playwright tests" checkbox yet because it's still used in release-pipeline.yaml. Once we decide to get rid of Mercurial 3 and 6 testing and only run tests on Mercurial 6, then that will also be the time to get rid of the "Run Playwright tests" checkbox as it will no longer have a use.

[hahn-kev]

I'd like this to actually use 2 jobs, instead of abusing the matrix to define 2 jobs in one job.

[myieye]

A couple little things 🙂

Requested changes completed, Kevin is busy with other things so I'm not going to ask him for re-review just now

[myieye]

From my testing, this seems to be working:

• Dotnet and Playwright (the only one where I picked self-hosted against develop, so the tests actually ran): https://github.com/sillsdev/languageforge-lexbox/actions/runs/9496684715/job/26171631307
• Only Playwright: https://github.com/sillsdev/languageforge-lexbox/actions/runs/9496617697/job/26171413933
• Only Dotnet: https://github.com/sillsdev/languageforge-lexbox/actions/runs/9496604033
• Neither 😉 https://github.com/sillsdev/languageforge-lexbox/actions/runs/9496572076

The results in Testspace confuse me a bit, but...they're there? https://sillsdev.testspace.com/spaces/275968/metrics

[hahn-kev]

It looks like there's some kind of bug in test space causing it to lose the os name on the matrix folder for dotnet tests, not sure what's going on there.

Tim the dotnet only run seems to have given up, can you make an issue for that?

[rmunn]

I've seen the dotnet test run hang on the self-hosted test runner, usually during the dotnet restore step. Seems to happen maybe one time out of three? Often enough that I end up half-expecting it, anyway. Haven't seen that happen on the GitHub-hosted runners. I have seen similar behavior running dotnet restore locally when my VPN connection to Dallas is up and active, so I'm inclined to think that there's a network issue in Dallas that's causing this. At any rate, I don't think it's something that can be solved with a test configuration change, so I'm going to go ahead and merge this.