Ship the custom node binary build with atom-shell.

This is required by the child_process.fork, which is indeed executing
the node binary to start a script.

The node fork can be found at:
https://github.com/atom/cefode-node/tree/chromium-v8

script/update

@@ -4,6 +4,8 @@ set -e
 
 cd "$(dirname "$0")/.."
 
+./script/update-node v0.10.5
+
 gyp --depth . atom.gyp \
   -Ivendor/brightray/brightray.gypi \
   -Dtarget_arch=ia32 \

script/update-node

@@ -0,0 +1,31 @@
+#!/bin/bash
+
+set -e
+
+cd "$(dirname $0)/.."
+
+NODE_VERSION=v0.10.5
+[ -z $1 ] || NODE_VERSION=$1
+
+# Test whether we need update.
+if [ -f "node/node" ] && [[ `node/node --version` == $NODE_VERSION ]] ; then
+  exit 0
+fi
+
+case $OSTYPE in
+  darwin*) NODE_PLATFORM=darwin ;;
+  linux*) NODE_PLATFORM=linux ;;
+  *) echo "Unsupported platform $OSTYPE" && exit 1 ;;
+esac
+
+NODE_DIST_NAME="node-$NODE_VERSION-$NODE_PLATFORM-x86"
+
+# Download node and untar
+NODE_TARBALL_URL="https://gh-contractor-zcbenz.s3.amazonaws.com/node/dist/$NODE_DIST_NAME.tar.gz"
+TARGET_DIR='node'
+[ -d "$TARGET_DIR" ] || mkdir "$TARGET_DIR"
+cd "$TARGET_DIR"
+curl -fsSkL $NODE_TARBALL_URL | tar -zx || exit 1
+
+cp "$NODE_DIST_NAME/bin/node" .
+rm -rf "$NODE_DIST_NAME"