podman: podman doesn't honour `init_path` for its pause containers

Issue Description

Changing the init_path parameter in container.conf results in containers using a different init binary than the default (catatonit). However, pause containers created within pods still require catatonit (unless infra_image is explicitly passed). This generates an error if catatonit is not found in the system.

NOTE: since catatonit is GPLv3, it must be replaced in some systems.

Steps to reproduce the issue

Steps to reproduce the issue

1. Install an alternative container init system (e.g. tini) and uninstall catatonit
2. Point init_path to the new init binary (e.g. /usr/bin/tini)
3. Launch a pod (e.g. podman kube play manifest.yml)

Describe the results you received

Error: image for service container: building local pause image: finding pause binary: exec: "catatonit": executable file not found in $PATH

Describe the results you expected

The pod starts normally, using the new init system for the containers.

podman info output

podman >= 4

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes