Provide option to store rationale on IPFS

[l-br1]

to make it easier for DReps to submit votes we should expand the storing options for rationales.

Proposed flow:

1. DRep writes rationale and confirms
2. We show modal with two options:
   a. 'Store the rationale yourself'
   b. 'Govtool Stores it for you on IPFS'

If they select option A, flow is the same as now, if they select option B then:

• We show a new step in the modal where
  • we still recommend them to download the file to reupload it on IPFS if Govtool service is not available in the future (and we link to guide to explain the process)
  • We show the URI and recommend to re-pin the file from their side (as extra decentralisation measure)
  • Clicking 'submit vote' will submit the vote with the rationale saved on IPFS

@Ryun1 please add technical details of how Govtool passes the file to IPFS and then gets the URI
@l-br1 add quick wireframe of flow

[Ryun1]

Govtool Stores it for you on IPFS

I would frame it as
'GovTool will pin your file to IPFS'
'which will make it accessible via the IPFS network'

because its not stored on IPFS
its stored by an IPFS node, and is accessible via the IPFS network

We show the URI and recommend to re-pin the file from their side (as extra decentralisation measure)

yup, GovTool will show the raw IPFS URI
and tell them to use their pinning service of choice to re-pin
we can recommend using Blockfrost and NMKR via the guides

If they select option A

Technically
GovTool can use Pinata pinning service, which will store the file on the pinata's IPFS nodes
Pinata offers a npm package with good docs
so it should be straight forward to implement

we still recommend them to download the file to reupload it on IPFS if Govtool service is not available in the future (and we link to guide to explain the process)

this is important to get right

[l-br1]