Add a LocationUtils class to give all Chromium Android code access to location helpers.

device/bluetooth/android/java/src/org/chromium/device/bluetooth/Wrappers.java

Index: device/bluetooth/android/java/src/org/chromium/device/bluetooth/Wrappers.java
diff --git a/device/bluetooth/android/java/src/org/chromium/device/bluetooth/Wrappers.java b/device/bluetooth/android/java/src/org/chromium/device/bluetooth/Wrappers.java
index 2cc705d22253d5a993bd2581f333c082b6478d4f..155897c18fd0ca600f4eb221b1bba9829f9fb35e 100644
--- a/device/bluetooth/android/java/src/org/chromium/device/bluetooth/Wrappers.java
+++ b/device/bluetooth/android/java/src/org/chromium/device/bluetooth/Wrappers.java
@@ -25,11 +25,11 @@ import android.content.IntentFilter;
 import android.content.pm.PackageManager;
 import android.os.Build;
 import android.os.ParcelUuid;
-import android.os.Process;
 
 import org.chromium.base.Log;
 import org.chromium.base.annotations.CalledByNative;
 import org.chromium.base.annotations.JNINamespace;
+import org.chromium.components.location.LocationUtils;
 
 import java.util.ArrayList;
 import java.util.HashMap;
@@ -162,9 +162,8 @@ class Wrappers {
             mContext = context;
         }
 
-        public boolean checkPermission(String permission) {
-            return mContext.checkPermission(permission, Process.myPid(), Process.myUid())
-                    == PackageManager.PERMISSION_GRANTED;
+        public boolean hasAndroidLocationPermission() {

[scheib, 2016/06/22 19:36:50]

The wrappers were designed to be the thinnest practical wrapper around the
Android classes. There are one or two examples of deviation (e.g.
getBluetoothClass_getDeviceClass), but they represent an API call and then
another call on the returned object.

This change adds a new concept to the wrapper that the android class doesn't
have, which I don't like. I see two main options:

1) Access LocationUtils.getInstance() and have test code able to set expected
behavior for it in test executables.

2) Sticking with this wrapper design, reworking as such:

To get virtual abstraction the wrappers need to be via a passed instance of an
object that is constructed elsewhere from code that knows if the executable is
production or test. Right now it is the adapter wrapper that is passed in to
ChromeBluetoothAdapter.java's constructor.

LocationUtils is a concept outside of the Adapter hierarchy, so we need a
wrapper for it passed in somehow.

A solution is to pass to ChromeBluetoothAdapter a new thing we create
'device.Wrappers' instance. That instance would have members for an
BluetoothAdapterWrapper and LocationUtilsWrapper.

[ortuno, 2016/06/27 21:05:53]

Follow up patch here: http://crrev.com/2100313003

Adds a new test function that uses LocationUtils.setFactory to control
LocationUtils from tests. LocationUtils still requires a Context. For that, the
patch removes ContextWrapper from Wrappers and modifies FakeContext to extend
MockContext. We can then pass the mock context directly to LocationUtils.

+            return LocationUtils.getInstance().hasAndroidLocationPermission(mContext);
         }
 
         public Intent registerReceiver(BroadcastReceiver receiver, IntentFilter filter) {