Some preparation work for easier development

**Summary**:
* Separation of client (aka the haxelib command) and the server (aka lib.haxe.org) -- all output which will be run on the server is now in the `server` folder
* Removed the SQLlite file from the repository. And empty file will automatically be created when the server starts the first time.
* Created a command-line tool which clean up the uploads and temporary files. Resets the database.
* The command-line tool also packages some very simple Haxe libraries from the `testing/libraries` folder into zipfiles, creates users for every library and submits them to the local haxelib server.

**Benefits**:
* Every time some screws the database up he could reset it and get's a clean start.
* Every one works with the same libraries during development and the libraries actually do work.
* When implementing new features the developer could add another library into the `testing/libraries` folder to show off how his new feature work to every one who checks out a new version.


TODO: Maybe someone should test this on Windows before.