Support podman

[yorickdowne]

What I did

Add logic that detects podman and sets .env variables accordingly. A user with both docker and podman installed would be using podman, if the podman socket is available, and Docker otherwise.

Logging in compose files no longer specifies a driver, and uses fields that both Docker and Podman support. Specifically, the log tag changes from '{{.ImageName}}|{{.Name}}|{{.ImageFullID}}|{{.FullID}}' to '{{.ImageName}}|{{.Name}}|{{.ID}}'

[yorickdowne]

Networking in podman is very challenging. This does not currently work well and should be revisited with Podman 6 in late May / early June.

[yorickdowne]

Archer tested this, and their findings are:
"I went ahead and compiled the incoming podman & passt/pasta/pesto & netavark/aardvark-dns, and this is what I get now:

INFO p2p: Connected peers inboundQUIC=166 inboundTCP=11 outboundQUIC=12 outboundTCP=22 target=200 total=211

This is without modifying anything on eth-docker side, also inter-container communication works as expected

So incoming podman 6 should be good to use for rootless mode, the only change needed would be using the new containers.conf option rootless_network_port_forwarder="pasta" "

Documentation would need to note that this is v4-only, it does not work with v6 dual-stack