feat!: SSX and w3up integration

[codynhat]

Description

Updates @geo-web/content to 0.5.x, which contains Ceramic performance improvements and new integration with w3up and SSX. Using the new w3up and UCAN required some changes to how we use SIWE. There must now be an actual nonce generated on the server, with a server verifying the SIWE signature before issuing a UCAN to allow a user to upload content to our web3.storage space.

This contains a breaking change in the content layer. Writes to content using this Cadastre is not backwards compatible with older versions of @geo-web/content. The corresponding PR for the browser should be deployed before this one to ensure compatibility.

Issue

https://github.com/Geo-Web-Project/js-geo-web/issues/10

Checklist:

• [x] My commit message follows the Conventional Commits specification
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have tested my code
• [x] My changes generate no new warnings
• [x] My PR is rebased off the most recent develop branch
• [x] My PR is opened against the develop branch

Additional comments

Please post additional comments in this section if you have them, otherwise delete it

Alert Reviewers

@tnrdd @gravenp

[tnrdd]

Works nicely on my end too. All the configuration done in pages/index.tsx to set w3InvocationConfig doesn't even affect loading time!