Use SIGWINCH for reached code profiler

The use of SIGURG conflicts with the sampling profiler, which is
already using that signal to drive stack sampling on Android. SIGWINCH
appears to be otherwise unused in ART, bionic, and Chrome.

Bug: 1136547
Change-Id: Iadecaebd383e4b39ba547c8a9cd5d0ebf6ae640a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2469459Reviewed-by: ssid <ssid@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Auto-Submit: Mike Wittman <wittman@chromium.org>
Commit-Queue: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#818202}

base/android/reached_code_profiler.cc

@@ -62,7 +62,7 @@ constexpr const char kDumpToFileFlag[] = "reached-code-profiler-dump-to-file";
 
 constexpr uint64_t kIterationsBeforeSkipping = 50;
 constexpr uint64_t kIterationsBetweenUpdates = 100;
-constexpr int kProfilerSignal = SIGURG;
+constexpr int kProfilerSignal = SIGWINCH;
 
 constexpr base::TimeDelta kSamplingInterval =
     base::TimeDelta::FromMilliseconds(10);