Workaround AR StrictMode violation

Works around a StrictMode violation coming from ArCore by allowing disk
writes when checking for ArCore APK availability.

Bug: 1038757
Change-Id: I0fbc469d243d89e14068b5d9ab3fca19999f122b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986246Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728069}

chrome/android/java/src/org/chromium/chrome/browser/vr/ArCoreShimImpl.java

@@ -38,7 +38,10 @@ class ArCoreShimImpl implements ArCoreShim {
     public @Availability int checkAvailability(Context applicationContext) {
         // ARCore's checkAvailability reads shared preferences via ArCoreContentProvider, need to
         // turn off strict mode to allow that.
-        try (StrictModeContext ignored = StrictModeContext.allowDiskReads()) {
+        // TODO(https://crbug.com/1038757): Remove the disk write context when the disk write is
+        // fixed on ArCore's end.
+        try (StrictModeContext ignored = StrictModeContext.allowDiskReads();
+                StrictModeContext ignored2 = StrictModeContext.allowDiskWrites()) {
             ArCoreApk.Availability availability =
                     ArCoreApk.getInstance().checkAvailability(applicationContext);
             return mapArCoreApkAvailability(availability);