Node Proxy Management

- Created `server_v2.js`
  - `server_v2.js` manages the proxy connections between the websockets and MPD instances
  - Usage:
    - Make sure to `npm install`
    - `node server_v2.js`
    - Eventually this will need to be run as a background service. This will mpst likely be done with [forever](http://blog.nodejitsu.com/keep-a-nodejs-server-up-with-forever/).
- Created `client_v2.js`
  - `client_v2.js` was used for testing the server during development. It takes user input and makes the necessary REST calls that will eventually be made by Java. PR #19
  - Usage:
    - Make sure to `npm install`
    - `node client_v2.js`
    - Commands:
      - `create host port pass` to make the REST call to create a Proxy
      - `destroy connectionID` to destroy the given Proxy
      - `quit` to quit the client.
- Updated play, pause, and stop components as a WIP example
  - The main purpose of this is to show how to use `'use strict';` in javascript and the JSLint options.
  - @nmont is working on a socket service that will create a single socket for all the components to use, and this will likely be overwritten and updated with that PR.
  - Normally for a PR, the `/* jslint devel: true */` would be removed, the `console.log` statements would be removed, and the code would be updated to pass JSLint/JSHint.
Yep. As it says, @nmont is working on a socket service that will create a single socket for all the components to use. His PR will change that. I'm leaving it in as an example. It doesn't necessarily hurt anything to leave the log statements in there; it's just generally bad to be logging things in a completed product.