Use Timecop for making time work "properly"

By freezing time, we will be sure that the times we set for tests
doesn't advance before the tests against those same times execute.
Timecop simply makes sure that the time looks like it is fixed at some
point in time.  Now all references to now will return the same value
since time won't be advancing and things will "just work."

Possible Conflicts:
	Gemfile
	Gemfile.lock
Player model tests.

These tests check that the player model can properly keep track of all
the values that it is given.
Initial player tests.

These are a very good start to getting player tests written and are
based largely on the tests for the other models.  I'm sure there will
need to be additional tests written as we find unique use cases for
this model that we haven't really tried to consider, yet.
Tests for matches.

These are a good set of tests for matches being displayed explicitly
and through the player views.  There will be more listed in the
matches views, but this is a very good start.
Final tests for course.

These are the final set of tests I was able to produce for the course.
There are likely other good tests to be had, but we've run out of
time.  Alas.  More tests will appear in the production version of the
code.
Compile fix
Fix nasty bug in match validation test

I wasn't generating matches correctly and so the tests were blowing up
pretty badly for everyone.  This should hopefully fix the issue.
Merge branch 'master' of https://github.com/geisler/game_contest_server

Conflicts:
	Gemfile.lock
	spec/models/contest_spec.rb
	spec/models/player_spec.rb
passing most test