Interrupting Foreman service start up can break future service start up because of server.pid

[ekohl]

When running systemctl restart foreman and interrupting it with ctrl+c can leave behind a tmp/pids/server.pid. That breaks future service start up. This is probably because we mount a volume since 82e5415 where previously it wasn't persisted between runs.

Various options:

• https://github.com/theforeman/foreman/blob/develop/extras/containers/entrypoint.sh has a step to remove the pid
• Rails 7.2 made the pid optional and disabled for for non-development (rails/rails@482330d)
• Implement ActiveStorage in Foreman and disable the mounted tmp volume

[evgeni]

This can also happen when you just kill the VM running Foreman, which is something that can happen