Notifications - persistence and use for more than just tasks

[usingtechnology]

For the activity log and tasks, we should create it's own persistence layer. Right now, we are simply querying proof and connection tables for certain states. If a partner is removed, then we would remove all the history of connecting (which may be a valid thing to store). Also, persistence would allow the end user to hide/remove items from the Activity Log.

Also, we should revamp the notification system to include automated cases. For instance, when a partner is auto-added, or presentation is auto accepted/handled. Notifications can be classified to indicate task versus activity (so the user knows understands to open the Activity log to see what has happened.)

[swcurran]

Agreed on the persistence -- IMHO -- the secure storage in the Agent should only be used for current agent activities (ledger objects/private keys, connections, held credentials, in-flight protocol state objects). Persistence beyond that should be in a controller (e.g. BPA) database -- linkages between connections and contacts/partners, presentations requested/provided, credentials issued, etc.