Podman logs don't recover from closed network connection

[Chrisss93]

I'm testing out running testcontainers-go HEAD with podman 4.2.0 using the latest changes from #414 . I am running podman on MacOS through qemu virtualization using podman machine. I'm not sure if its in this project's power to fix this it but its worth mentioning that when testcontainers-go is reading logs from a podman container, it can no longer recover from closed network errors (these tend to be frequent in these sorts of docker-on-vm type setups). Against a regular docker daemon, testcontainers-go would seamlessly observe the closed network error and re-request the container logs since the time it observed the error (#323, #369).

Annoyingly I expect the reason this doesn't work with podman might be because docker defines its ContainerLogsOptions with the Since field as string while podman defines its ContainerLogsOptions with the Since field as a time.Time.
One of the reasons this part of testcontainers-go might not work on podman+MacOS is due the host machine and qemu VM clock-times becoming desynchronized (containers/podman#11541). However, even after this is accounted for (manually set the clock-time on the qemu VM to match the host), re-requesting logs still doesn't work...