fixed #12063 - use less heavy code in executor tests

[firewave]

The allocation invokes some heavy ValueFlow computations. We just want to generate an unconditional error from the analysis so use some lighter code which does the same.

TestThreadExecutorFiles::deadlock_with_many_errors

Before:

real    0m23.517s
user    0m33.453s
sys     0m2.297s

After:

real    0m5.051s
user    0m6.234s
sys     0m0.422s

[firewave]

This might fix the random executor test timeouts tracked in https://trac.cppcheck.net/ticket/12063 which might just be actual timeouts since the tests are slow and we might have just encountered a slow runner.

[firewave]

This might fix the random executor test timeouts tracked in https://trac.cppcheck.net/ticket/12063 which might just be actual timeouts since the tests are slow and we might have just encountered a slow runner.

Some before cases:

 48/100 Test  #46: TestProcessExecutorFiles .............   Passed   67.76 sec
 49/100 Test  #47: TestProcessExecutorFS ................   Passed   67.99 sec

 48/100 Test  #46: TestProcessExecutorFiles .............   Passed   76.17 sec
 49/100 Test  #47: TestProcessExecutorFS ................   Passed   76.80 sec

 48/100 Test  #46: TestProcessExecutorFiles .............   Passed   83.89 sec
 49/100 Test  #47: TestProcessExecutorFS ................   Passed   84.90 sec

It appears my assumption might be correct as these are starting to cutting it close to the 90 seconds timeout.