Suppress StrictMode warning reading command line file.

The command line file is only ever read on debuggable builds, so
it doesn't really matter if we trigger strict mode warnings to do it.

To avoid the log spam, disable strict mode around the file read.

Bug:17313418
Change-Id: I659d8b42459bfecc299374b774405e952a74bf2d
diff --git a/chromium/java/com/android/webview/chromium/WebViewChromiumFactoryProvider.java b/chromium/java/com/android/webview/chromium/WebViewChromiumFactoryProvider.java
index 99f68fa..2a29ce4 100644
--- a/chromium/java/com/android/webview/chromium/WebViewChromiumFactoryProvider.java
+++ b/chromium/java/com/android/webview/chromium/WebViewChromiumFactoryProvider.java
@@ -26,6 +26,7 @@
 import android.os.Build;
 import android.os.FileUtils;
 import android.os.Looper;
+import android.os.StrictMode;
 import android.os.SystemProperties;
 import android.os.Trace;
 import android.util.Log;
@@ -203,7 +204,10 @@
         }
 
         if (Build.IS_DEBUGGABLE) {
+            // Suppress the StrictMode violation as this codepath is only hit on debugglable builds.
+            StrictMode.ThreadPolicy oldPolicy = StrictMode.allowThreadDiskReads();
             CommandLine.initFromFile(COMMAND_LINE_FILE);
+            StrictMode.setThreadPolicy(oldPolicy);
         } else {
             CommandLine.init(null);
         }