Update docs on --sig-proxy

Docker deliberately does not proxy SIGCHLD. SIGSTOP and SIGKILL are also not proxied, given they cannot be caught and always affect the receiving process. SIGKILL in particular is a frequently-used signal, and it is likely confusing that it is not proxied to the container, and instead just kills the client process. Update docs to note this behavior to prevent confusion.