Recreate container if image is updated

[elya5]

Describe the bug I'm not sure whether this is actually considered a bug but I expected podman-compose to destroy and create a new container when the image is updated and the up command is called. Might be related to #56.

To Reproduce Steps to reproduce the behavior:

1. podman-compose up -d
2. podman-compose build
3. podman-compose up -d

Expected behavior Recreation of containers with outdated image.

Actual behavior Old containers keep running.

Environment:

• OS: Fedora 35
• podman version: 3.4.4
• podman compose version: 1.0.3