Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph

o Changes priority of ORDER BY...LIMIT (PlanBuilder.TopX) so it is executed
  before updating the graph
o Changes so TopPipeBuilder waits for aggregation, but not for return
  expressions execution
o UpdateActionBuilder waits on slice to be done before accepting work
o SliceBuilder does not wait for updates to be done
Merge pull request #813 from systay/795

Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph
Revert "Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph"

This reverts commit b9814528621c95b2f4e8552f96ed3442fc18175a.
Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph

o SlicePipe will now empty the remainder if it is an updating query
Merge pull request #815 from systay/795

Fixes #795 - Inconsistent behaviour when using LIMIT and updates
Reintroduce 33725b268d8a7a024d55e2a65b3a338b488e6824
Update breaking test so that it passes with this change.
Random change of new URI() to URI.create()
Revert "Fixes #795 - Inconsistent behaviour when using ORDER BY and LIMIT while updating the graph"

This reverts commit f299aa394be4563d3724573547b04f39ce6c4517.

Reverted because it is too close to GA and a workaround exists. Will be included again after the upcoming release.
Merge pull request #816 from digitalstain/server-log

Reintroduce 33725b268d8a7a024d55e2a65b3a338b488e6824
Remove potential race condition
Ensure that all config files have double newlines at the end