MetalLB addon fails to deploy on Podman

### Current Behavior

If `kind` is configured to use Podman instead of Docker when creating a test environment with the `metallb` addon enabled, the create will fail with:

```console
$ ktf env create --addon metallb
building new environment kong-testing-environment
Error: failed to deploy addon metallb: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/kong-testing-environment-control-plane/json": dial unix /var/run/docker.sock: connect: permission denied
```

If the addon is not enabled, the environment will succeed.

### Expected Behavior

Kind itself supports Podman as a container runtime, so we should for KTF as well.

### Steps To Reproduce

```markdown
$ ktf env create --addon metall
```

### Kong Kubernetes Testing Framework Version

```shell
`v0.44.0`
```

### Kubernetes version

```shell
`v1.27.3`
```

Start at the `ktf env create --addon metallb` entry point and trace how the MetalLB addon connects to the container runtime when kind uses Podman. Reproduce the failure with Podman and verify that creating an environment with the MetalLB addon succeeds without attempting an inaccessible Docker socket.

Written by the indexing model from the issue text.