Feature request: a way to prevent a specific test_id from resubmitting

[hagertnl]

I am using a setup where I have multiple instances of the same test being run in parallel out of the same applications directory. The traditional method to stop tests is by adding the .kill_test file to Scripts (or run --mode stop, which does the same thing). However, I may not want to kill all instances of the same test, I may just want to kill one.

I could certainly just cancel the job in the scheduler, that would put an end to it, but I'd like a harness-provided mechanism that I can prevent a specific test_id from resubmitting. I am okay if it's as simple as adding a .kill_test to that test's Run_Archive directory, and if that has to be done by hand.

I think multiple asynchronous runs are becoming a more prevalent use case of the harness, so this flexibility would be very nice.