Resurrect chrome_update_manifest properly, updating it for manifest-groups

This starts from what we currently run in production (roughly
290c32b024e3acbb1a4a5d318b819190ef8d5322), and reworks the script in full.

The reason for ressurection beyond it still being ran in production basically
comes down to the fact it's in the way for migration to googlesource.com,
and it's a bit... wrong... to have required production code not in vcs for
multiple quarters.

To ease maintenance, and avoid issues like this in the future, this script is
reworked to just do includes- this additionally will reduce the frequency of
updates to the manifest repository.

CQ-DEPEND=CL:40201

BUG=chromium-os:32407,chromium-os:37471
TEST=chrome_update_manifest -r /some-workspace # no output should occur,
     # aside from some known warnings about duplicates in DEPS.git
TEST=chrome_update_manifest -r /some-workspace --verbose # debug
     # mode; should see output.
TEST=sync tests; comparing before/after for internal and external.
TEST=chrome_update_manifest --internal-manifest-url /path/to/local/checkout
     <usual args>
TEST=chrome_update_manifest --external-manifest-url /path/to/local/checkout
     <usual args>

Change-Id: I1e7ed8283941e77c8a40765cadfb269fbdf91cba
Reviewed-on: https://gerrit.chromium.org/gerrit/26892
Commit-Queue: Brian Harring <ferringb@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Brian Harring <ferringb@chromium.org>

1 files changed, 1 insertions, 0 deletions

diff --git a/bin/chrome_update_manifest b/bin/chrome_update_manifest
new file mode 120000
index 000000000..72196ceea
--- /dev/null
+++ b/bin/chrome_update_manifest
@@ -0,0 +1 @@
+../scripts/wrapper.py
\ No newline at end of file