Consolidating duplicate excluded tests

[adamfarley]

Commenting out duplicate tests from the exclude files, ensuring the platforms are appended to their unexcluded duplicates, and tidying the targets to help avoid this problem in the future.

See here for details:

#4650

[adamfarley]

Duplicates have been removed. Tidying now.

[karianna]

@adamfarley Lots of failing test?

[smlambert]

We need to update our workflows (captured in #2299)

• to not run all the tests when these files change
• to ensure Github runners are configured with up-to-date prereqs

Will not block this PR on those failures. (Jenkins Grinder run as a better test for this PR than using run-aqa in a workflow).

[adamfarley]

@adamfarley Lots of failing test?

Ok, got a theory vis-a-vis the failures:

Looking at a bunch of other PRs in this repo (including this one, which is also an exclude file change), it seems that these tests aren't run for any other PRs.

My theory is that, since this PR started out as a WIP PR, it triggered the test jobs (via the github action "Directories/Files Change Test PR") when I took the WIP out of the title and clicked the "ready for review" button.

So, in short, I think we should merge this PR as-is, and raise 2 separate issues for the following problems (to be addressed AFTER the release ofc):

1. That the Git action for these tests appears to have been designed to run on every PR, and is instead only run when someone changes a PR from draft to ready-for-review. If we are meant to be running these tests for every PR, this needs fixing.
2. That there are a number of issues in these tests which need to be solved. Some issues look familiar, so perhaps they're all already solved and the fixes just need to be integrated into the Git action.

Update: Shelley beat me to it. :)