Add Docker cleanup strategy to prevent storage drift on Pi/server

Pitch

Each deploy creates a new container (old one is explicitly removed),
orphaning its logs and leaving dangling images from the local build.
On a Pi/server with limited storage this accumulates silently.

Technical suggestions

Two options to discuss:

• Deploy-time: add a docker system prune -f task in the engine role
  (or deploy-engines playbook), runs on each deploy
• Cron: add a periodic docker system prune -f in engine_cron role,
  decoupled from deploy

Note: avoid docker system prune -af in cron — would delete local tagged
images if container is temporarily stopped.

Inspect the engine role, deploy-engines playbook, and engine_cron role to compare where cleanup could run. First resolve whether cleanup belongs at deploy time or on a cron, then define validation for docker system prune -f while preserving local tagged images; the issue is done when one approach is selected and implemented safely.