legacy log file search returns now correct section header

fixes the problem where a query for an entry in legacy log files with multiple entries per day shows in response the correct entry but with the wrong section header/timestamp.
part of ticket 1109081
moved whois-logsearch, api/abusec and api/acl into whois-internal module
e2e pending route
edited changes.txt
fix for Issue #56
moved api and abusec to whois-internal
dropped Audience, JettyConfig, copypasted Logsearch jettybootstrap
Don't log empty apiKeys
Added integration tests for ACL limits from the Whois REST API.
fix - jar shading causes duplicate class warnings in maven

problem is identical to http://stackoverflow.com/questions/14402745/duplicate-classes-in-commons-collections-and-commons-beanutils. To avoid duplicate class problem, the commons-beanutils dependency was excluded from the poms of the modules that do the jar shading, as suggested here http://stackoverflow.com/questions/9802736/maven-build-warning-we-have-a-duplicate-class.

also removed not needed dependencies (log4j and aspectj related) that caused the same duplicate class warnings during shading
using getKey instead of toString for correct rebuild of route6 trees
show some more detail of error - JdbcExportDao
edited changes.txt and added --valid-syntax and direct route lookup to comparison_queries
added mnt-route parsing test cases
Finished migrating internal API to whois-internal
Migrated RestClient to static helper class
Merge branch 'master' of github.com:RIPE-NCC/whois

Conflicts:
	changes.txt
	whois-commons/pom.xml
added redirect urls for rdap
Merge branch 'master' into rdap
Merge branch 'master' into rdap