reduce logging in preparation for production deployment
attempt to tone down some more verbose logging
remove filtering of src/test/resources that overrides log4j.properties
reduce some more logging
reduce more logging
only audit actions that require authentication
Add ANNOTATION_READ action to make it possible to lock down reading of
annotations if necessary
restrict updating of users based on the username they are trying to
update, or failing that, if they could create a user from scratch, with
a backup that they always have to be authenticated
cleanup and security audit
change default redirect to be the index page, instead of the ontology
manager page
more security auditing, to allow annotation read to be authenticated if
necessary using configuration

currently, these changes have no effect, as the given permissions were
unauthenticated already