Remove stopped containers

[mike12345567]

Description

Bringing back the old mechanism of removing stopped containers.

This was added in: #15089
Then removed in: 04cb51e

We are having issues with stopped containers blocking tests from running so attempting to add this back in.

Failure example: https://github.com/Budibase/budibase/actions/runs/12355464244/job/34486039531

Following issue seems related: testcontainers/testcontainers-node#881

Solution (temporary)

For anyone following the issue above/experiencing the same issue - the eventual problem/solution was that Github has started rolling out ubuntu-latest to 24.04 from 22.04. For some reason on this new version of Ubuntu test containers fails to find the images by hash, attempting to re-create them continuously eventually leading to test failure.

For now we have switched from running our Github runners on ubuntu-latest to ubuntu-22.04 as this gets us up and running, while we investigate the issues with test containers.

References:

1. Github begins rollout of new images on the 5th of December - Ubuntu-latest workflows will use Ubuntu-24.04 image actions/runner-images#10636
2. Release of new image actually occurs on 12th of December - https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20241211.1
3. Last successful CI run operating on Ubuntu 22.04 - https://github.com/Budibase/budibase/actions/runs/12320310076/job/34389276222
   
4. First failing CI run operating on Ubuntu 24.04 - https://github.com/Budibase/budibase/actions/runs/12355464244/job/34486039531
   

[qa-wolf]

QA Wolf here! As you write new code it's important that your test coverage is keeping up.
Click here to request test coverage for this PR!

[adrinr]

Good finding!