getContainerConfig() is null when docker storage is overlayfs

**Describe the bug**
With new fresh installs of docker, the new storage default is `overlayfs`, instead of the deprecated `overlay2` [source](https://forums.docker.com/t/overlay2-not-enabled-by-default-with-get-docker-com-on-ubuntu-lts-24-04/150471) This causes `getContainerConfig` to throw a null pointer exception

**To Reproduce**
Freshly install the latest docker version, and try run intergration tests with microshed, this causes the null pointer to happen, updating the docker daemon.json at `/etc/docker/daemon.json` with

```
{
"storage-driver": "overlay2",
"features": {
"containerd-snapshotter": false
}
}
```
Allows it to use the old storage, and enables the IT's to work again

**Expected behavior**
For it to not throw a null pointer when using newer versions of docker storage

**System information:**
- OS: [Windows, WSL(Ubuntu)]
- Java Version: [11, 17]
- MicroShed Testing Version: [e.g. 0.9.2]

**Additional context**
From my research an option is to swap from `getContainerConfig` to `getConfig` should work, but unsure, happy to test if there is a beta release to confirm

Locate getContainerConfig and the related getConfig call, then reproduce the integration-test failure with Docker using the overlayfs storage default. Check how the container configuration is obtained and run the MicroShed integration tests; done means the overlayfs setup no longer causes a null pointer exception and the tests pass.

Written by the indexing model from the issue text.