Propagate Medusa process exit code in k8s docker-entrypoint

[c3-clement]

Resolve #805

Prior to this change, if the Medusa process exits with a non-zero exit code for some reason, the Medusa container will be stuck forever because of the while true loop.

With this fix, the while loop will be interrupted if the Medusa process exits, and the container will exit with the same code as the Medusa process exit code.

To validate this change, I've manually tested the following scenarios:

• Start the medusa container without any file at /etc/medusa.ini -> the container should exit with a non-zero code.
• Start the medusa container with a valid config at /etc/medusa.ini -> the container should run as expected.
• Change the config /etc/medusa.ini while the container is running -> the container should exit with a zero code.
• Put an arbitrary sys.exit(42) in server.py to mock a production issue -> the container should exit with the status code 42.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[adejanovski]

LGTM, thanks for the fix @c3-clement !