Move to the new web3 storage API

[salieflewis]

We're using the old API currently to handle IPFS storage via uploadBlob and uploadFile, this API is being deprecated in January so we need to move to the new one. I imagine it is quite similar.

[salieflewis]

The legacy web3.storage upload API, pinning service API, and w3name will sunset on January 9, 2024.

All uploads to the legacy web3.storage prior to January 9, 2024 will continue to be stored until further notice, though over time latency and availability may degrade.

https://blog.web3.storage/posts/the-data-layer-is-here-with-the-new-web3-storage

[salieflewis]

Here is the first pass at integrating with the new API.

https://gist.github.com/salieflewis/bbba37daba7acd0edff39ff32e32a72d

I'm not sure the library is setup to work seamlessly in a React environment, currently running into this error which has been noted by another developer.

[salieflewis]

Currently waiting for more documentation around the new API to make this change. This includes frontend examples and potentially helper packages that will give us more flexibility in a React environment.

[salieflewis]

Closing in favor of #281

Ultimately we have until January 9th to make this migration, but that is right around the corner. Having spent a lot of time toying around with multiple implementations and attempts to move to the new web3.storage API I think it makes more sense to use Pinata.

List of reasons are:

The docs are dense, introduce a lot of new terminology that is used inconsistently, ultimately making it hard to understand what is going on
There aren't enough examples of using the new API across a range of development environments
The console (website) isn't complete
Using UCANs feels like overkill for what we currently need