message: Fix incorrect log messages in NativeProcessLinux (pr40588)
  The "signal" argument was removed from the MonitorCallback function, but
  not from the log statements within it. This wasn't noticed because the
  name "signal" suddenly started referring to the libc function with that
  name.
  This fixes that.
diff: @@ -412,9 +412,9 @@ void NativeProcessLinux::MonitorCallback(lldb::pid_t pid, bool exited,
  // Handle when the thread exits.
  if (exited) {
  LLDB_LOG(log,
  - "got exit signal({0}) , tid = {1} ({2} main thread), process "
  + "got exit status({0}) , tid = {1} ({2} main thread), process "
  "state = {3}",
  - signal, pid, is_main_thread ? "is" : "is not", GetState());
  + status, pid, is_main_thread ? "is" : "is not", GetState());
  // This is a thread that exited. Ensure we're not tracking it anymore.
  StopTrackingThread(pid);
  @@ -495,9 +495,9 @@ void NativeProcessLinux::MonitorCallback(lldb::pid_t pid, bool exited,
  const bool thread_found = StopTrackingThread(pid);
  LLDB_LOG(log,
  - "GetSignalInfo failed: {0}, tid = {1}, signal = {2}, "
  + "GetSignalInfo failed: {0}, tid = {1}, status = {2}, "
  "status = {3}, main_thread = {4}, thread_found: {5}",
  - info_err, pid, signal, status, is_main_thread, thread_found);
  + info_err, pid, status, status, is_main_thread, thread_found);
  if (is_main_thread) {
  // Notify the delegate - our process is not available but appears to
  