Fix service process to not idle-timeout if Chromoting is enabled.

Fix service process to not idle-timeout if Chromoting is enabled.

When Chromoting is enabled via Chrome, the service process is started
if necessary and notified that the Chromoting service has become enabled.
When the service process is later auto-started (or run manually) it will
initialize Chromoting, which detects that it is enabled and starts up, but
fails to inform the service process that it's enabled, so the process waits
a while and then exits.

BUG=73168
TEST=Enable Chromoting in Chrome.  Kill the existing service process and start a new one manually.  Ensure that the new one runs for at least two minutes without quitting.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=75381

[Wez, 2011-02-17 11:27:37]

Trivial short-term fix to keep the service process alive if it auto-starts and
Chromoting is enabled but Cloud Print is not.

(I'm working on a more substantial CL to make more of the
enable/disable/start/stop logic common across services, to simplify this)

[Alpha Left Google, 2011-02-17 11:28:40]

LGTM.

[sanjeevr, 2011-02-17 19:05:51]

LGTM

[Sergey Ulanov, 2011-02-17 19:20:54]

LGTM