Change 2/3 Add Encapsulation for Game.player to remove message chaining

There existed classes that extended Tile that required more information on the Player object to perform its functionality. To retrieve the Player, these Tile classes would have to retrieve the Game object from the Tile’s level, and finally retrieve the Player object from Game.  To remove this long message chain, a method getPlayer() was added to the Level class.  The getPlayer() method localizes the chain of retrieves and returns the Player object needed to the caller.

The Player object inside of the Game class was changed from public to private, as well as its’ getter and setter was added to the Game class.  This ensures the encapsulation of a critical Game element that should never be exposed as public.

Removed some message chaining by making Game.player private. Level now uses game.getPlayer() method.

Within the Level class, Level has a getPlayer() method which delegates to the game object's getPlayer method.

```java
public Player getPlayer() {
		return this.game.getPlayer();
}
```

In the future, the same concept could be used to encapsulate Level.game, which is currently accessed publicly.