CORE-3882: began modifying the notification agent to use a relational database

Work Remaining:

- replace obsolete OSM calls with database queries
- examine existing services to ensure that the code still makes sense

Note that existing obsolete OSM calls are currently commented out using the #_
reader macro, which provides a handy marker for future changes to make.
CORE-3882: more changes to migrate the notification agent to a relational database

Work remaining:
- examine services to ensure they still make sense
- use lein-kibit to check for non-idiomatic code
- use lein-eastwood to check for broken code
CORE-3882: some refactoring and code cleanup
CORE-3882: fixed several bugs that I found during testing
CORE-3882: added the recording of email notifications
CORE-3882: bumped the version number
CORE-3882: updated the README
replaced clojure.data.json with cheshire
replaced notification-agent.json with cheshire.core
CORE-3882: add the seen and deleted flags back into notifications
CORE-3929: switched to the latest version of iplant-clojure-commons
CORE-3969: modified the notification agent to work with the new database schema
CORE-4031: fixed the extraction of the email address in notification-agent.notifications/add-email-request
upped dependencies and version

clojure -> 1.5.1
clojure-commons -> 1.4.1-SNAPSHOT
kameleon -> 0.1.1-SNAPSHOT
lein-iplant-rpm -> 1.4.1-SNAPSHOT
Merge branch 'dev' into 1.8

Conflicts:
	src/notification_agent/job_status.clj
CORE-3969: correctly handle display names containing empty strings
CORE-4032: accept and report types of "tool request"
CORE-4127, CORE-4130, CORE-4128, CORE-4129, CORE-4132: Began adding the
database functions for CRUD operations on system notifications.
Added an endpoint for adding a system notification and for getting a
system notification.
Filtered out unneeded fields from responses and reformatted the
timestamps that get returned.