Wrap all containers using dumb-init for smart signal handling

[chriswessels]

Bug report from hollaAtChaBoi:

I thought it was an arbitrum specific issue, where it wouldn't shutdown gracefully after receiving the sigterm command from kubernetes (i.e. kubectl delete pod).
But it turns out that the command wasn't actually receiving the signal and when I exec into the pod and run kill it shuts down fine
and I also noticed the graphnode pods exhibit the same behavior
killing the process with pid 7 shuts it down correctly, so im guessing with the current construction of the pods kubernetes is sending it to the process with pid 1 (haven't tested that specifically)