Add algorithms.coffee, change Node app to restify, etc.

coffee/algorithms.coffee exists to hold the avoidance/search algorithms
to be implemented. Lazy avoidance is already implemented, and seems to
be working well enough for what it does. I just had one game where the
ship made it to 2855 turns - no joke. I will likely document a few of
the arrangements of asteroids which are essentially guaranteed death to
the ship - they're really quite simple, and from my observations these
are generally the situations where lazy avoidance leads the ship to
death. Although, every so often the ship will seem to just sit there and
get taken out by asteroids as soon as they come close (i.e. the ship
doesn't even move) -- this will take some investigating. Probably
because of the fact that lazy avoidance only looks to find spots where
the ship won't be immediately struck -- so it could start moving away
and then move back in, and get trapped. Might take that into account...

I still have to work on the Node MySQL linkage to store the game reports
into a database. I would just use sqlite locally (actually, that might
be better...) except that since this is going to run on my FranTech box,
I only have 30GB of space there, and don't want to see what happens if I
were to run up against that limit. Ehh... TBD.

The next thing to do will be implementing either A* or MDLBFS algorithm,
and provide some way of deciding which to use (other than `Env.algorithm
= "astar"'). Probably by making /astar and /mdlbfs routes which serve up
modified index.html files that set the algorithm? Or use different
init.js files setting the algorithm as needed?

But yeah... almost 3000 turns on lazy avoidance. Damn.
Look a little deeper for second move in lazy avoidance...
Add sqlite data collection.
Make asteroids come in from all eight directions.