* Use a new, currently empty `Board#winner?` method as our loop
  condition
* Add `Player#insignia` so we can print the correct player insignia
  depending on who the current player is
* Print the board and a prompt for coordinates
* Switch the current player after a player finishes moving

Return the actual board in the right format instead of always returning
3 rows of 3 dots.

Also add `Board#update_cell` to facilitate player movement.

Add an `initialize` method to get rid of our test errors and use the
constants we created in 231060de4c493a9c6ba3510a9be4d405517af5c6 when
creating new `Player`s.

Test some code for an API concept for player, ideas for tests of the
`Player#move` method.

We shouldn't be requiring all our files & classes in the spec_helper. It
should just be used for test setup. We can require the modules we need
for testing directly in the test files.

Take string coordinates in the form ":integer:,:integer:" and convert
them to [integer, integer]. We'll be using these converted coordinate
values to place a piece on the board.

Don't print the grid directly. We'll do this in a separate display
method or game loop area.