Implement caching of Ceramic/IPFS content

[gravenp]

To help address performance challenges with the content layer on the Cadastre UX, we should explore & implement simple caching of content per user session.

This will create a potential delay between updates being made and them being reflected on the Cadastre, but that is a reasonable tradeoff for now given the small number of parcels and rate of content change.

• Cache parcel content in the browser after the first load of the user's session
• Make updates to the cached content based on any changes that the user makes to their parcels
• Add a refresh button (https://fonts.google.com/icons?icon.query=refresh) to the header section of the parcel details panel (next to the copy link to parcel icon) that allows the user to trigger a manual fetch of content for the selected parcel

[gravenp]

Working as intended with standard Ceramic caching.