fixes #135 may break other untested stuff :(

service did not add updated entries, since it identified entries on
*only* id - which ofc would be the same on a updated entry. Added a
check on the update date aswell.
Bails if an entry cannot be found in elastic #104
Checks if an entry exists, e.g. is a update #104
Finds related entries to a updated Entry #104
Removes updated and related entries from varnish #104

removed the ban all since that would be contraproductive when we later
tries to ban with precision :)
Merge remote-tracking branch 'origin/develop' into feature/104_invalidate_caches
Adds Rättsinformationsförordningen for testing #104

with related entries
handles malformed URIs also #104

just return no related for a malformed uri / other errors
Adds a updated entry in a feed for testing #104

To use this you're supposed to import
testfeeds/regression/rattsinformationsforordningen first
Update must be newer then knownstoppingentry #104

otherwise, it's not an update. this might result in some problems when
collecting feeds from different sources in irregular intervals.. hmm

also, make sure all old entries are in the feed, otherwise they will be
considered deleted.
Makes the testfeed not "logical complete" #104

Having the header tag <fh:complete/> makes the feed "reset" itself. By
removing it I can have a much smaller testfeed.
Merge branch 'develop' into feature/104_invalidate_caches
datetime formatting broke the test #135

WOOOPS. Should had written it TDD style :rolleyes:
Merge branch 'feature/104_invalidate_caches' into develop