Don't start services when swank-js is required

By default swank-js starts a server as soon as it is required.  Instead export functions to start the servers, and
remove the default behavior of relying on argv.
Don't kill the server if the client chooses to run the swank:quit command

* Remove custom quit_lisp handler
* Add built-in quit-lisp handler
* Provide self and response object to custom methods so they can accomplish more
* Deal with quit message from handler
* Note: if the client reconnects, they will have the same context as previous client
Give REPL clients access to the global context, and limit stacktraces to where the repl call ends
Don't log anything to console

Better is to rewrite these calls to use some other function that conditionally does logging.
Make completion work in global context
Start Swank servers if not loaded via require
If syntax errors occur during evaluation, trim the evalcx part of the trace
Merge pull request #65 from mwolson/attachable-server

Embed swank-js within existing node.js server