`make unit-test` leaves behind containers

[BenjaminPelletier]

Describe the bug
After make unit-test completes, it leaves behind containers that interfere with a local DSS deployment.

To reproduce

• Start with no containers
• make unit-test from repo root
• docker container ls -> 6 containers

Difference from expected behavior
When unit testing is complete, it should clean up after itself or else print a message telling the user how to clean up.

Possible solution
If these containers are cheap to bring up, then make unit-test should probably just destroy the containers after running the necessary tests.

If these containers are relatively expensive to bring up and/or a developer will likely run unit tests many times with one set of containers, perhaps add another make command to clean up and print that information as the last thing make unit-test does.

[the-glu]

I'm not able to reproduce locally, witch containers are left running?

Notice that the DB ones take a few seconds to be removed in my case, but they are gone after 15-30s.

[BenjaminPelletier]

If our container behavior isn't reliable, that's an even bigger problem. make unit-test doesn't leave behind containers on your local system?

[the-glu]

Hum:

It's seems to be random. I was able to reproduce it one time, tried again without stdout redirection to debug and back on to confirm, and it's only failed to cleanup the first attend.

[the-glu]

Ok, I added cleanup when fixture is done beeing used in #1514

Locally containers are gone immediately (minus testcontainers/ryuk) when tests are done, so I do assume it should work.

I ran tests 5 times and didn't see any leftover, but it's probably better if you do the test on your side, not sure how often I do have the issue.