fix(docker): ensure orphaned contributoor containers can be managed

[mattevans]

Problem:

Restarting Contributoor
Contributoor is not running, starting contributoor
ERRO[0002] failed to start service: failed to start containers: exit status 1
Output:  sentry Pulling
 sentry Pulled
 Network installer-0035_contributoor  Creating
 Network installer-0035_contributoor  Created
 Container contributoor  Creating
Error response from daemon: Conflict. The container name "/contributoor" is already in use by container "5bd18e54e72b1b9c38678b14dd6688fb67f2df15f705417e0b5f0b9c84b163ca". You have to remove (or rename) that container to be able to reuse that name.`

Our IsRunning() implementation only checks for active containers with the exact configuration it expects, if this has changed (say between versions), then IsRunning() will return false.

Likewise with Stop(). It'll only attempt to stop containers started with the exact configuration it was started with, if this has changed, then it won't stop the container.

IsRunning() + Stop() have been updated to fallback to checking via container name, not just relying on docker compose which expects consistent config.