Stop and remove containers if user cancels a simulation

[vtnate]

Any background context you want to provide?

When running tests developers often ctrl-c to cancel a test midway through a long-running simulation. The container is then left alive unnecessarily which is a resource drain.

What does this PR accomplish?

Catch KeyboardInterrupt while simulating and kill all containers from the gmt-om-runner image

How should this be manually tested?

• Start a simulation test
  • For instance tests/GMT_Lib/test_gmt_lib.py::test_simulate_cooling_plant
• ctrl-c once the simulation begins
• docker ps -a to check that containers from the image are removed

  What are the relevant tickets?

  Resolves #384

[vtnate]

@nllong I have a couple questions:

1. Is this functionality even necessary/valuable?
2. The rm compound command works as expected when I manually use it in the terminal, but in the code as written it fails with unknown shorthand flag: 'a' in -a when I use it. Am I not understanding how subprocess.run() works? I've confirmed that the split transforms to a list as expected.

[nllong]

@nllong I have a couple questions:

1. Is this functionality even necessary/valuable?
2. The rm compound command works as expected when I manually use it in the terminal, but in the code as written it fails with unknown shorthand flag: 'a' in -a when I use it. Am I not understanding how subprocess.run() works? I've confirmed that the split transforms to a list as expected.

I think I just experienced this myself, so yes to 1.

2. -- no idea!