Initialize the application context prior to initializing command line flags.

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=

Committed: https://crrev.com/5335d2564facbeea5368cfb188a0339e4699d71e
Cr-Commit-Position: refs/heads/master@{#316565}

[Peter Beverloo, 2015-02-16 16:32:56]

The use of application context is being introduced here:
  https://codereview.chromium.org/914373003/
  (see content_startup_flags.cc)

[Peter Beverloo, 2015-02-16 17:42:59]

peter@chromium.org changed reviewers:
+ nyquist@chromium.org, rmcilroy@chromium.org

[Peter Beverloo, 2015-02-16 17:42:59]

+nyquist for review
+rmcilroy, ppi for fyi

Who would be the appropriate reviewer for this? As mentioned, a need is being
introduced in https://codereview.chromium.org/914373003/, but that can be
refactored as well if this isn't ideal, although it feels fairly harmless to me.

[ppi, 2015-02-16 17:55:44]

lgtm, sounds reasonable

[Peter Beverloo, 2015-02-16 17:57:04]

The CQ bit was checked by peter@chromium.org

[commit-bot: I haz the power, 2015-02-16 17:57:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/925423002/20001

[Miguel Garcia, 2015-02-16 18:00:40]

miguelg@chromium.org changed reviewers:
+ miguelg@chromium.org

[Miguel Garcia, 2015-02-16 18:00:40]

lgtm

[rmcilroy, 2015-02-16 18:01:28]

On 2015/02/16 18:00:40, Miguel Garcia wrote:
> lgtm

lgtm.

[commit-bot: I haz the power, 2015-02-16 18:03:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-02-16 18:03:21]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Peter Beverloo, 2015-02-16 18:06:10]

On 2015/02/16 18:03:21, I haz the power (commit-bot) wrote:
> Try jobs failed on following builders:
>   chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

Hm. No European owners left for this code now that Ben left the team :-(.

Tommy, mind taking a look?

[Peter Beverloo, 2015-02-16 18:06:50]

peter@chromium.org changed reviewers:
+ tedchoc@chromium.org

[Peter Beverloo, 2015-02-16 18:06:50]

+tedchoc@chromium.org for OWNERS

[benm (inactive), 2015-02-17 12:18:04]

benm@chromium.org changed reviewers:
+ benm@chromium.org

[benm (inactive), 2015-02-17 12:18:05]

lgtm

owners stamp

[Peter Beverloo, 2015-02-17 12:18:45]

The CQ bit was checked by peter@chromium.org

[commit-bot: I haz the power, 2015-02-17 12:19:32]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/925423002/20001

[commit-bot: I haz the power, 2015-02-17 12:22:26]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-02-17 12:23:18]

Patchset 2 (id:??) landed as
https://crrev.com/5335d2564facbeea5368cfb188a0339e4699d71e
Cr-Commit-Position: refs/heads/master@{#316565}