loman: Handle projects not marked as workon if remote set
loman: Handle projects not marked as workon if remote set

This handles the case where a project listed in the manifest is
sent without options.workon set but has options.remote set. This can
happend if 2 projects are listed in an ebuild, and only 1 of them is
actually remote.

BUG=None
TEST=verified that the remote project is handled as a remote one and
the manifest project is properly handled as a normal workon project.

Change-Id: I09563787586bd8dbdfee7ab0bd6a9bc82d41cd32
Signed-off-by: Rhyland Klein <9c6f026f68ffecc44f215af186ef513cd72b6ce4@nvidia.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/37021
Reviewed-by: Brian Harring <fdc2d0a2e2340b623587cee5ea8dff425d1eb1f3@chromium.org>
Commit-Ready: Brian Harring <fdc2d0a2e2340b623587cee5ea8dff425d1eb1f3@chromium.org>

zhang0137/chromite,bpsinc-native/src_third_party_chromite,coreos/chromite,zhang0137/chromite,chadversary/chromiumos.chromite,bpsinc-native/src_third_party_chromite,coreos/chromite,coreos/chromite,chadversary/chromiumos.chromite,bpsinc-native/src_third_party_chromite,zhang0137/chromite