Ensured woodman exports itself as window.woodman in mixed environments

Even when the library is used in an AMD application, users may still
want to have Woodman be globally accessible and referenced so that
modules do not have it as a dependency.
"initialize" and "start" functions exposed on global Woodman object

The "load" function combines "initialize" and "start" functions.
After further thoughts, it remains useful to separate the two
concepts so as to initialize Woodman's config in a separate file
and to start it in the "main" function of the app.
Added devDependencies and dependency to socket.io