Android Chromoting: Don't auto-reconnect if connection was established.

Android Chromoting: Don't auto-reconnect if connection was established.

If the Linux host is killed (due to changing PIN or other reason), the
Android client sees that the connection has failed with error
PEER_IS_OFFLINE. This is the same error that would occur if the JID
were stale, which the client normally handles by auto-reloading the
host-list and reconnecting. But since the session was already
connected, the Desktop activity does not properly get torn down and
re-initialized (which is something to address at a future date).

This CL fixes the linked bug by ensuring that the automatic reload does
not happen after a successful connection.

BUG=424759
Committed: https://crrev.com/95543b346a8712aa97226a5201d9c1df0ce34807
Cr-Commit-Position: refs/heads/master@{#316686}

[Lambros, 2015-02-14 02:21:42]

lambroslambrou@chromium.org changed reviewers:
+ jamiewalch@chromium.org

[Jamie, 2015-02-17 22:22:20]

lgtm

[Lambros, 2015-02-17 22:32:28]

The CQ bit was checked by lambroslambrou@chromium.org

[commit-bot: I haz the power, 2015-02-17 22:33:15]

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

[commit-bot: I haz the power, 2015-02-17 22:50:14]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-17 22:50:40]

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