🍈 Unify application context usage.

base/android/java/src/org/chromium/base/BaseChromiumApplication.java

Index: base/android/java/src/org/chromium/base/BaseChromiumApplication.java
diff --git a/base/android/java/src/org/chromium/base/BaseChromiumApplication.java b/base/android/java/src/org/chromium/base/BaseChromiumApplication.java
index 77c63adff04fd93742259d00ce932b81c8ede05d..3c38b61df14b0a01a77455bd5a4a579e9280bfb1 100644
--- a/base/android/java/src/org/chromium/base/BaseChromiumApplication.java
+++ b/base/android/java/src/org/chromium/base/BaseChromiumApplication.java
@@ -113,6 +113,7 @@ public class BaseChromiumApplication extends Application {
     public void onCreate() {
         super.onCreate();
 
+        ContextUtils.setApplicationContext(this);

[Torne, 2016/04/13 15:38:38]

I really don't like depending on BaseChromiumApplication here. That won't work
for WebView, and the general goal of the other refactorings is to eliminate
BaseChromiumApplication from base entirely (we shouldn't be depending on an
Application subclass for global initialisation).

[Peter Wen, 2016/04/13 18:49:20]

Oooh, makes sense. Removed. I'll add it where it makes sense then.

         if (mShouldInitializeApplicationStatusTracking) startTrackingApplicationStatus();
     }