Klever

At the moment schedulers request Bridge for changes in jobs and tasks periodically. This is not efficient since first this introduces delays that become too much today after many optimizations were made in Klever 2.0 and second this introduces some resources overhead since it is quite hard to do and handle HTTP requests. Although a decision (using some message queue) was suggested a long ago, now we can and should to implement it.