Add support for PHP built-in web server.

Add also default configuration for database.
Created Ranking\Entity\Match test case in PHPUnit.

A match is the object that holds information of when players have
played, whom they played with, where (the map) they played.
Currently I am creating a match with only one *creator*, but a
game to be valid (in - I hope - a near future) should be created
or corroborated/moderated by more than 50% of its players.
Created getters in Ranking\Entity\Match.

- All the getters created to satisfy the previous tests
- Map and User entities were given a new __toString() magic method (yata!)
- Match test provider now makes better use of the recently done __toString()
  implementations
- Match were already created with some simple Doctrine 2 @annotations
Created basic setters/getters for Ranking\Entity\Match

- Basic entities cover these properties: id, played (datetime),
  created (datetime), creator (Ranking\Entity\User) and
  map (Ranking\Entity\Map)
- Replaced the old getter test for more descriptive and simple
  solutions. Simple is always better for unit tests.

No exceptions for validations were tested, this is pretty uggly.
We are still missing the property that will hold the played of
that given match in a soon commit. Please pandas, work, work and
work! Or no bamboo for you today!
Created exceptions tests for Match setters

- Setters for DateTime instances now have a type hint since
  I don't support all date declarations Respect\Validation
  supports and that would break Doctrine 2 Entity Manager
- PHP errors for values other than the type hint also tested

Still missing the property that will hold the relationship between
users (players) and a match.
Created tests for __toString methods in User and Map entities.

- Map entity also gained a new method that returns the map name
  validator to be used in the tests;
- The tests now used Respect\Validation and its great Exception
  messages, I (strongly) suggest that if you are reading this
  and didn't see that, try and mess with the test value to see
  what went wrong;
Created Ranking\Entity\Team to be used in Matches.

- Comment block in provider for invalid password length in User
  test
- Match entity now has defined column names compatible with
  Respect Relational
- Unit tests covering 100% of Team entity
- Doctrine 2 mappings for entity Team (column names already
  compatible with Relational)

Instead of using a Many-to-Many relationship I opted by a
One-to-Many/Many-To-One relationship between 3 entities. I have
a little feeling that this will help a more scalable development
rather than user a N-N.
Tests and attribute for holding the Team entity collection are
still missing though.
Fix same column name used for two different properties in Team entity.
Fixed typo in RANKING_ENVIROnMENT.

TODO: Fix later the class name and other typos found in code.
Added relationship between Match and Players = Team.

- Added scape characters to match table name
- Made constructors initializing Doctrine's ArrayCollection() in the
  relationships
- Created relationship in Match for many Teams
- Created relationship in Team for a Match and a Player (User)
Created Ranking\Entity\Match::getTeams() method.
Fixed environment variable name fixed in a previous typo.

My bad! Fixed the typo in a previous commit and forgot about the tests.
Changed /users/<id> to /users/<username>.

- Created tests
- Changed link from user registration
- Implemented changes to get information by user name instead of
  user id
- In public/index.php
    - Added `use` to shorten class usage
    - Added user name validator to the user route /users/*
    - Changed routine to not add user information if it already set
Fixed link to user's home navigation (when logged in)
Created 404 html template to be used when a user is not found.

The 404 template accepts a *msg* variable that is used in the
HTML title and the H1 title. Some little text is there to help
the user that get's this page.
There is also a link to the project GitHub issues panel.
Typo in 404.html: ProbablY
Created Ranking\Entity\Team::filterRace to normalize race strings.

Since the race attribute is a plain string, it can come in many
different forms: Arm, arm, ARM, aRM, etc...
This *filter* method normalizes it to: Arm.
Tests were also added to assure that.
Created Ranking\Entity\Match::addTeam()

- Better code coverage for Map, Team and Match entities tests
Created Ranking\Entity\User::setId to be used when defining teams.

- Created also the getIdValidator() used to validate IDs of users
- Created unit tests to keep up the 100% code coverage of this
  class

This validator could (and probably will) be used in many different
controllers/routes, much of that use would be in the Match routes.
Created basic controler for /users/*/matches

The controller already has tests and validates inputs like:
- when the match was played
- which players played it
- which map was played on
- the winning team
The next steps could be:
- Controller to handle user to team transformation
- Recording match into the database presuming a FFA match, each
  player is an independent team
- Making the user/player validation better in a match, searching
  for the currently logger user in the player list of a match,
  we will add him later on or somewhere into the space-time.