Initialize the application context prior to initializing command line…

… flags.

We used to initialize the command line flags prior to setting the
application context in Android's BrowserStartupController.

When determining the command line flags for the renderer, certain flags
may be dependent on the Android SDK version being used. Getting this value
through base::android::BuildInfo requires the application context to be known.

This change makes sure that we initialize the application context prior to
calling the native SetCommandLineFlags function.

BUG=

Review URL: https://codereview.chromium.org/925423002

Cr-Commit-Position: refs/heads/master@{#316565}

content/public/android/java/src/org/chromium/content/browser/BrowserStartupController.java

@@ -283,8 +283,8 @@ void prepareToStartBrowserProcess(boolean singleProcess) throws ProcessInitExcep
         // Now we really need to have the resources ready.
         resourceExtractor.waitForCompletion();
 
-        nativeSetCommandLineFlags(singleProcess, nativeIsPluginEnabled() ? getPlugins() : null);
         ContentMain.initApplicationContext(appContext);
+        nativeSetCommandLineFlags(singleProcess, nativeIsPluginEnabled() ? getPlugins() : null);
     }
 
     /**
@@ -294,6 +294,8 @@ public void initChromiumBrowserProcessForTests() {
         ResourceExtractor resourceExtractor = ResourceExtractor.get(mContext);
         resourceExtractor.startExtractingResources();
         resourceExtractor.waitForCompletion();
+
+        ContentMain.initApplicationContext(mContext.getApplicationContext());
         nativeSetCommandLineFlags(false, null);
     }