LoadLotsOfFiles can now run in parallel with the HFIR tests
and the file list can end up trying to load files that the HFIR
tests have already deleted.

Without this protection the script cannot be used in
conjunction with the multiprocessing module on Windows.

* Refs #23346 convention now known after sort; added to system test

* Refs #23346 add to release notes

* Refs #23346 reword release note

The test required that a found peak was in a specific
position in the table but this is not guarnateed any longer
after bd4b4e3c. The test failure
was not spotted on the original pull request as it was skipped
due to memory limitations on the node.

Some tests were still failing because different modules are writing in the same directories, using the same files names.
There are at least 3 different locations the tests write to:
1. build/ExternalData/Testing/Data/SystemTest
2. build/Testing/SystemTests/scripts
3. build
In some cases a process tries to write to a file that already exists (same name used by another test).
In other cases a process performs a .cleanup() which removes a file that is still needed by a running test.
The solution was to group the tests in lists where all modules starting with the same 4 letters are given to one
core. This worsens the load balance between cores (with 8 cores, core 1 performs 93 tests while core 8 only has 44).
This is not ideal but allows the suite to complete without failures.
The runtime using 8 cores goes down from 2h to 30min, which is ok as a first step.

Increase VERY_BIG_NUMBER to a maximum.
Validate the type of input workspace.
Parallelise the main loop.
Include the workspace index into an error message.
etc...

Force ReflectometryISIS to use version 1 of FindReflectometryLines.

Re #22734

Use the '-j 8' option to run on 8 cpus.

There are now two different modes of console output:
- the full mode where all output from the tests are printed (this is the old behaviour)
- the quiet mode (activated by the '-q' or '--quiet' option) that just prints the progress

Refs #23298

This is done to avoid cleanup failures. Some data files were being deleted by another process
while the current process running a test in the same module using the same file had not yet finished.