Copy Linux me2me script to output dir for GN builds

remoting/host/linux/remoting_me2me_host_wrapper.sh

Index: remoting/host/linux/remoting_me2me_host_wrapper.sh
diff --git a/remoting/host/linux/remoting_me2me_host_wrapper.sh b/remoting/host/linux/remoting_me2me_host_wrapper.sh
new file mode 100755
index 0000000000000000000000000000000000000000..cde1d5b80e57ba1bc038a5c568d97ebed36a6a9f
--- /dev/null
+++ b/remoting/host/linux/remoting_me2me_host_wrapper.sh
@@ -0,0 +1,18 @@
+#!/bin/sh
+
+# Copyright 2016 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# This is a simple wrapper script around the remoting_me2me_host binary,
+# intended only for development use. It is copied into a build
+# subdirectory as
+# $CHROMIUM_OUTPUT_DIR/remoting/chrome-remote-desktop-host
+# and runs the remoting_me2me_host binary in the parent output directory.
+# The linux_me2me_host.py script is also copied into the remoting/
+# build directory, so it finds this host wrapper script in the same
+# directory.
+
+# cwd cannot be used since it is set to $HOME when chrome-remote-desktop

[Sergey Ulanov, 2016/04/18 22:48:01]

This is not the only reason to avoid CWD. Scripts should never rely on CWD to
locate relative paths to other files. Running ./dir/foo.sh should have the same
effect as ./foo.sh . Just remove this comment?

[Lambros, 2016/04/18 23:45:53]

Yep, removed.

+# is daemonized.
+exec "$(dirname "$0")/../remoting_me2me_host" "$@"