Always use --host-resolver-rules Chrome flag with ChromeOS

Always use --host-resolver-rules Chrome flag with ChromeOS

From the bug description:

A recent change inadvertently changed the flags that ChromeOS had used. The change:

   Handle replay args within replay module.
   https://codereview.chromium.org/617043003/

Made that the --host-resolver-rules is not added when --netsim is used. However, prior to the change, --host-resolver-rules was always used with ChromeOS.

I am unsure why ChromeOS always uses that flag. However, it matches how the cros_browser_backend always sets the DNS ports to None.

BUG=423092
Committed: https://crrev.com/a61c2280f97f17f01c4020c8e880dfc6e8fd1535
Cr-Commit-Position: refs/heads/master@{#299537}

[slamm, 2014-10-13 21:14:36]

slamm@chromium.org changed reviewers:
+ nednguyen@google.com, tonyg@chromium.org

[slamm, 2014-10-13 21:14:36]

Restore ChromeOS behavior of always using --host-resolver-rules.

Does anyone happen to know why ChromeOS always uses --host-resolver-rules?

[nednguyen, 2014-10-13 21:16:38]

nednguyen@google.com changed reviewers:
+ achuith@chromium.org

[nednguyen, 2014-10-13 21:24:16]

nednguyen@google.com changed reviewers:
- tonyg@chromium.org

[slamm, 2014-10-14 17:16:57]

Hi Achuith,

PTAL. It is the same change that you LGTM'd in my other CL:

Handle replay args within replay module.
https://codereview.chromium.org/617043003/

-slamm

[achuithb, 2014-10-14 18:39:52]

lgtm

I'm not too familiar with this code, but will keep an eye out for breakages.

[slamm, 2014-10-14 18:59:56]

The CQ bit was checked by slamm@chromium.org

[commit-bot: I haz the power, 2014-10-14 19:01:48]

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

[commit-bot: I haz the power, 2014-10-14 20:28:53]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-14 20:30:11]

Patchset 1 (id:??) landed as
https://crrev.com/a61c2280f97f17f01c4020c8e880dfc6e8fd1535
Cr-Commit-Position: refs/heads/master@{#299537}