The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a83632457ce535445b2089deafb4f959934fb9ee

commit a83632457ce535445b2089deafb4f959934fb9ee
Author: Yuwei Huang <yuweih@chromium.org>
Date: Thu Feb 01 20:01:54 2018

[Remoting Host] Make SignalingAddress accept new LCS JID format

We have added the `chromoting_lcs_` prefix to resource of an LCS JID. The
current code in SignalingAddress doesn't recognize the new format and
will believe the the new format is of XMPP connection.

This currently doesn't cause any issue after we change the format on
server and client because:
* For reply scenario, the connection type will be determined from the
  `from-channel` field instead of the JID format.
* For outgoing messages, the IQ message format is basically the same for
  LCS and XMPP connections, so IT2ME still magically works even though
  SignalingAddress believes the connection type is XMPP.

This CL cleans up the type inferring logic in SignalingAddress so that
future developers will not misuse it.

Bug:  798902 
Change-Id: I66d5d1af4c7510d2dd2775769689288a9f2333e9
Reviewed-on: https://chromium-review.googlesource.com/889984
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#533788}
[modify] https://crrev.com/a83632457ce535445b2089deafb4f959934fb9ee/remoting/signaling/signaling_address.cc
[modify] https://crrev.com/a83632457ce535445b2089deafb4f959934fb9ee/remoting/signaling/signaling_address_unittest.cc