Forward oop-r flags to renderer for crashes

The renderer doesn't use these flags, so this is just a temporary
mechanism for crash visibility.

Right now there are some number of crashes that are happening on
platforms where OOP-R is not turned on (e.g. Windows), and it would be
helpful to verify in the short term that OOP-R is being turned on
deliberately via a command line flag vs accidentally.

These should be removed once OOP-R is shipping by default everywhere.

Bug: 757605
Change-Id: Ib5a1a1d49939851b71563762409ac0fc0ba05ede
Reviewed-on: https://chromium-review.googlesource.com/1178570Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583838}

content/browser/renderer_host/render_process_host_impl.cc

@@ -2787,6 +2787,7 @@ void RenderProcessHostImpl::PropagateBrowserCommandLineToRenderer(
     switches::kDisableLogging,
     switches::kDisableMediaSuspend,
     switches::kDisableNotifications,
+    switches::kDisableOopRasterization,
     switches::kDisableOriginTrialControlledBlinkFeatures,
     switches::kDisablePepper3DImageChromium,
     switches::kDisablePermissionsAPI,
@@ -2816,6 +2817,7 @@ void RenderProcessHostImpl::PropagateBrowserCommandLineToRenderer(
     switches::kEnableLCDText,
     switches::kEnableLogging,
     switches::kEnableNetworkInformationDownlinkMax,
+    switches::kEnableOopRasterization,
     switches::kEnablePluginPlaceholderTesting,
     switches::kEnablePreciseMemoryInfo,
     switches::kEnablePrintBrowser,