[api] avoid leaking connections in threads

I assume this is a bug in clockwork, but it's easy to work around
[webui] Added more testcases for adding reviewer in requests
[api] catch errors while fetching lastnotifications

There is no harm done - we just refetch later again
[dist] add (api) coverage to the README
[api] add a test for the status_history model

It was meant as finger training in coverage, but it actually found a nasty
bug I introduced in my refactoring
[api] move the matcher out of activexml

It has no coverage outside of test cases
[webui] test cases for comment post methods
[api] ignore indices files for coverage

They are config files really
[backend][api] drop BUILD_UNCHANGED event

 90% of our events are "build unchanged" and we have zero subscribers
add $BSConfig::workerpartitionservers

Currently evaluated in scheduler, should be read and transmitted
by the src server in the future.
[backend] delete no longer needed line
[backend][api] drop BUILD_UNCHANGED event

 90% of our events are "build unchanged" and we have zero subscribers
[api] fake issue servers using webmock

Fetching fate issues seems to be a stub ;(
[dist] update gem versions
[api] move the ldap code from user model to a class of its own

It has unfortunately 0 coverage, so I can't test it - but at
least I can filter it out and make sure the rest is covered well
[api] really test delayed jobs
[api] notifications for new comments now being sent out to hermes
[backend] return 'delayed' when an aggregate has to be delayed

Fixes the scheduler looping over the same project.
[webui] avoid multiline status lights for a partition
[api] refactor application controller