AJ-1915: align rawls-swat-test-job to what Rawls currently does

[davidangb]

Ticket: https://broadworkbench.atlassian.net/browse/AJ-1915

What:

three changes to the rawls-swat-test-job github action in this PR:

1. Upgrade broadinstitute/workflow-dispatch from v3 to v4. I have not tackled upgrading all usages of broadinstitute/workflow-dispatch in Sam; there are others still on v3.
2. Set a run-name value for each iteration of the test matrix. This solves the problem where the github action UI linked to the same terra-github-workflows test run for all three iterations of the matrix, making it much easier to navigate directly to a specific test suite.
3. Align the test matrix to what Rawls is currently using. Specifically, this removes the AJ tests which were running 0 tests and were removed in Rawls back in AJ-1549: streamline GHA swat tests rawls#2800, and it splits the workspaces tests into two groups for concurrency; this was done in [NO TICKET] Split workspaces-owned swat tests into 2 groups rawls#2897.

See Rawls' implementation at https://github.com/broadinstitute/rawls/blob/cf8c3fcff774dca5346e5596554098e1852ba78c/.github/workflows/rawls-build-tag-publish-and-run-tests.yaml#L158-L204.

Why:

Make swat tests more performant and more useful.

How:

Assuming Sam will continue to run Rawls and Orch swat tests, it would be great to centralize code to prevent divergence like this. I have not tried to tackle that in this PR.

---

PR checklist

• I've followed the instructions if I've made any changes to the API, especially if they're breaking changes
• I've filled out the Security Risk Assessment (requires Broad Internal network access) and attached the result to the JIRA ticket

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud