Clarify Child::kill behavior

```
Child::kill       == std Child::kill + Child::wait
Child::start_kill == std Child::kill
```

As a side note, kill that also waits, is convenient, but also
dangerous, because `wait` may hang in certain cases (NFS, ptrace,
etc).  And different behavior between std and tokio may leads to
bugs when code is mechanically converted from one to another.  Better
name name of this function might be `kill_and_wait`.

tokio/src/process/mod.rs

@@ -1164,7 +1164,13 @@ impl Child {
 
     /// Forces the child to exit.
     ///
-    /// This is equivalent to sending a `SIGKILL` on unix platforms.
+    /// This is equivalent to sending a `SIGKILL` on unix platforms
+    /// followed by [`wait(2)`](https://man7.org/linux/man-pages/man2/wait.2.html)
+    /// ([`Child::wait`]).
+    ///
+    /// Note: behavior of this function is different from std version of
+    /// [`Child::kill`](std::process::Child::kill): std version does not `wait`.
+    /// Tokio [`start_kill`](Child::start_kill) is equivalent to std `Child::kill`.
     ///
     /// # Examples
     ///