Persist offline records at the Apollo queue link level

[mdeitner]

Records (currently just Engagements) created offline are manually persisted to local storage. When the app regains internet access the records are sent to the proper view/hook so they can be persisted to the database.

This solution requires custom logic for each record type that we'd like to persist client side as well as logic to avoid duplicates with the Apollo cache.

A better solution might be to persist the records in a custom Apollo queue link.