BREAKING: Propagate signals to qdrant by changing command/args

[mac-chaffee]

Currently, the helm chart runs /bin/sh as PID 1 which does not catch signals or send them to child processes. As a result, when you delete a qdrant pod right now, it will take the full terminationGracePeriodSeconds and then get SIGKILLed.

NOTE FOR THE CHANGELOG:

This release includes a breaking change to the args value. Users who were overriding the default args with their own shell commands will now need to also set command: ['/bin/sh', '-c']. We recommend that you ensure signals are still being propagated to qdrant if you override args or command to ensure qdrant can shut down gracefully.

It is technically possible to make this a non-breaking change (use the old command if custom args are supplied), but I think it's unlikely users' custom args are capable of respecting signals with /bin/sh as PID 1.

[mac-chaffee]

Apparently just changing /bin/sh to /bin/bash + using exec is enough? Anyone know if it's true that bash and sh have different exec/signal handling? If so, we can make this a non-breaking change by just using bash+exec.

[mac-chaffee]

Superseded by #91