WIP: Test suite setup improvement

Refactored test suite setup
* Adjusted namespace definition in composer.json
* Corrected namespaces in Neo4jClientMock, as \ before fqdcn are not required when using namespaces correctly
* Added a .travis.yml file for using Travis and having a real db to test on
* Added a Import file to import data when the Slim bootstrap is done

I just need to look a bit deeper of how to bootstrap the app correctly for integration tests.

Running `phpunit` is ok.

Would be cool if merged to add `Travis` service webhook
Aha. I get it now.

I prefer, in Slim applications, to try and refactor all of the big processing and business logic out of `public/index.php` and into the service layer. Configuration (and dependency injection) should then be wholly responsible for handling environment management.

It's an excellent idea, but I'd like to try and stick with the Slim PHP paradigm as much as possible in this app.