Do not store the exit command in container config

[Luap99]

What this PR does / why we need it:

There is a problem with creating and storing the exit command when the
container was created. It only contains the options the container was
created with but NOT the options the container is started with. One
example would be a CNI network config. If I start a container once, then
change the cni config dir with --cni-config-dir ans start it a second
time it will start successfully. However the exit command still contains
the wrong --cni-config-dir because it was not updated.

To fix this we do not want to store the exit command at all. Instead we
create it every time the conmon process for the container is startet.
This guarantees us that the container cleanup process is startet with
the correct settings.

[NO NEW TESTS NEEDED]

How to verify it

Which issue(s) this PR fixes:

Special notes for your reviewer:

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Luap99]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Luap99]

@mheon PTAL

[mheon]

I'm now realizing that a large part of the original decision-making around Specgen was to keep Podman and Libpod unentangled, so Libpod could be used outside of podman (the new implementation enforces Podman-style CLI for the exit command). I don't think we care about this as much now, though.

Code LGTM.

[Luap99]

I'm now realizing that a large part of the original decision-making around Specgen was to keep Podman and Libpod unentangled, so Libpod could be used outside of podman (the new implementation enforces Podman-style CLI for the exit command). I don't think we care about this as much now, though.

That makes sense, thanks.

[rhatdan]

/lgtm