Dirty cache on update of profile information in Ceramic

[dysbulic]

What would you like to be added?

The Hasura updateSingle action should be triggered when profile information is updated in Ceramic (#920).

There are two separate documents used to store the profile information. Both could be retrieved when the cache is invalidated, but it would be more efficient to only pull the one that was changed.

This will be slightly more important when, eventually, the cache needs to be invalidated when a user adds a verified account.

Why is this needed?

The cache should be as up to date as reasonably possible, and invalidating it when changes are known is one way of doing that.

It is theoretically possible to update the cache with the values inputted for the profile, and not have to query the Ceramic network, but in practice this is error prone.

[dysbulic]

Currently when the cache reloads, it loads the contents of three streams: the basic profile, the extended profile, & the account attestations. Theoretically, when the cache is dirtied, the specific keys affected could be passed to the caching system & only the needed streams could be loaded.

This complexity is left to some future developer and for the time being we'll simply load all three.