Added Migrations mini framework.

Imported small framework from another project into this one to manage
database migrations simply and effectivey.

I think that it would be intelligent to use Javascript to run the front
end, and then provide a back end service exposed through a simple API to
deliver the 'goods'
Added player bodies migration

Added migration to hold info for player question bodies. Also note that
the name of the migration itself can't bemore than 32 characters.

I'm thining that the structure of the questions will be something like
this:

Title	The Question Title
p1_body	The question for user 1, (Write function to...)
p2_body The same thing as p1_body but for user 2
Added answers table to database.

Be sure to run migration script to update database to newest version.
Added answers table that will contain a reference to it's parent
question as well as a series of answers that goes with that question.
Which we could store as a serialized array or something simple like
that. That way when we do comparisons between what the javascript evals
to, we can just send it off and go.
Updated text on migration page.
Added Answer table alter migration.

Added inputs field to answers so there is something to pump into
whatever the functions of the questions are. Given the inputs provided
by the answer.
Merge branch 'migration'