Interrupting `cabal test` may leave test executable running

Using the following test that loops infinitely, starting `cabal test` then Ctrl+C it leaves the test executable running because the interrupt sent by cabal doesn't kill it.

```
module Main where

main :: IO ()
main = loop 1

loop :: Int -> IO ()
loop 0 = pure ()
loop n = loop (n + 1)
```

Using cabal 3.10.2.1

(Minimized from a Stackoverflow question: https://stackoverflow.com/questions/78357175/never-ending-quickcheck-test-leaves-running-process-even-after-interrupting-cab )

Start by reproducing the issue with the infinite-looping Main module shown in the report and run it through cabal test. Trace how Ctrl+C is handled and propagated from cabal to the test executable. Done means interrupting cabal test also terminates the running test process.

Written by the indexing model from the issue text.