Code review comment for lp://staging/~cjwatson/rabbitfixture/signal-esrch

I saw http://lpbuildbot.canonical.com/builders/lp-db-devel-xenial/builds/2297/steps/shell/logs/summary, which wasn't quite the exact failure mode I remembered noticing before, and asked myself "how could that happen?". Since the code immediately preceding that was a check for whether the process is still running, the obvious answer was that it must be a race: the process exited by itself between the check for whether it was still running and the attempt to send a signal to it.

The private `_signal` method is only used to send various signals to the process that are intended to terminate it, either cooperatively (`SIGTERM`) or abruptly (`SIGKILL`). Therefore, it is not a problem if the process has already gone away, and the right answer is to simply ignore errors that mean that.

Finally, since `rabbitfixture` hasn't yet dropped Python 2 support and I didn't want to block a fix for this bug on that, I looked up https://docs.python.org/3/library/exceptions.html to confirm that `ProcessLookupError` corresponds to `ESRCH` and used the old approach of catching `OSError` and filtering by `errno` rather than catching `ProcessLookupError` directly, since that's only two more lines of code.