Add services as a subtype of ModuleData

Services are modules that act like a pseudo-user and respond to commands.
They come "out of the box" with some useful functionality and shortcuts,
see service.Service for details.
Services are subclasses of ModuleData (instead of being their own seperate class)
because they need to make use of a number of module-level hooks, and it makes it easier
for the implementor if this is done automatically.

What is not implemented here:
    How to determine if a user is a service admin.
        Hopefully to be done later.
    Anything to do with cross-server management of services.
Create a test service testing basic service functionality

Put it under a new test/ directory for all such basic test modules.
Add admin operator permission lookup to services
services: Abstract sending a user a NOTICE with message splitting into a method tellUser()
service: Set host, ident and gecos on self.user

Allow subclass to set them custom, else default to nick and server name.
service: Fix a race cdn where a user might disconnect before we try to send them a message

This is mainly a problem in callbacks and stuff, but we put it in the helper function to keep it simple.
service: Handle nick collisions with our LocalUser

Bitch-slap the other user.
Move service.py out of core, into a "module library" file

This is due to concerns that service.py assumes too much for core code.
dbservice: A subclass of Service for services with a database connection
Add pymysql to requirement.txt

This is needed for db stuff to work
Pull in schema file + test data from master branch
Merge pull request #30 from ekimekim/db-services

Db services