Catch Throwable in shouldInterceptRequest.

We were only catching Exception which meant that other Throwables (often
OutOfMemoryError) were still crashing in the JNI bindings instead of
generating "nice" Java stacks.

Bug: 718929
Change-Id: I6c941002d632696c736aed9ad3304223d813c94b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2060671
Auto-Submit: Richard Coles <torne@chromium.org>
Commit-Queue: Tobias Sargeant <tobiasjs@chromium.org>
Reviewed-by: Tobias Sargeant <tobiasjs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743103}

android_webview/java/src/org/chromium/android_webview/AwContentsBackgroundThreadClient.java

@@ -32,7 +32,7 @@ public abstract class AwContentsBackgroundThreadClient {
                             isMainFrame, hasUserGesture, method, requestHeaderNames,
                             requestHeaderValues)),
                     /*raisedException=*/false);
-        } catch (Exception e) {
+        } catch (Throwable e) {
             Log.e(TAG,
                     "Client raised exception in shouldInterceptRequest. Re-throwing on UI thread.");