v0.0.11

• Added execution timeout

While upgrading EKS from 1.14 to 1.15, I ran into an issue where an in-flight request would hang, and thus the execution would never end. Restarting the pod fixed the issue, and while I'm not exactly sure why it happened, what I do know is that since there's no health check that the liveness probe can perform, adding a timeout to each execution and panicking on failure to respect that execution time limit is a safe way to either allow the pod to recover on its own, or if the issue keeps happening, then at least it will increase visibility.