Turn off `init_stack_vars` on Android.

On x86 as well as on ARM. It breaks Java test
`JavaBridgeCoercionTest.testPassNull`.

There is probably an underlying bug that we need to fix.

Bug: 1131993, 977230
Change-Id: Ie579516a06d13577fcb4a61fa515a2d873bfcd15
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429233Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@google.com>
Commit-Queue: Chris Palmer <palmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810834}

build/config/compiler/BUILD.gn

@@ -123,13 +123,12 @@ declare_args() {
   # recognizable in the debugger, and crashes on memory accesses through
   # uninitialized pointers.
   #
-  # TODO(crbug.com/977230): Enabling this when 'is_android' is true breaks
-  # content_shell_test_apk on android-kitkat-arm-rel. Enabling this when
-  # 'use_xcode_clang' is true may call an old clang that doesn't support
-  # auto-init.
-  init_stack_vars =
-      !(is_android && (target_cpu == "arm" || target_cpu == "arm64")) &&
-      !use_xcode_clang
+  # TODO(crbug.com/1131993): Enabling this when 'is_android' is true breaks
+  # content_shell_test_apk on both ARM and x86.
+  #
+  # TODO(crbug.com/977230): Enabling this when 'use_xcode_clang' is true may
+  # call an old clang that doesn't support auto-init.
+  init_stack_vars = !is_android && !use_xcode_clang
 
   # This argument is to control whether enabling text section splitting in the
   # final binary. When enabled, the separated text sections with prefix