Improve onboarding via OS-level protocol handler

Right now, IPFS Desktop installs system-wide protocol handlers (dweb, ipfs, ipns) which converts ipfs://<cid> URI to gateway URL and opens that in default browser.

It is fine, but may be confusing on the first use.

We could improve this behavior and show a dialog window, where user can choose how to open IPFS resource via radio-button-like selector:

• open from public gateway in the default web browser (default)
• open from a local gateway (show only if daemon in running)
• open in webui/Files (show only if daemon in running)
• open in webui/Explore (show only if daemon in running)
• (checkbox) remember the choice for the future
  • should be accompanied by a toggle in menubar menu: “Ask how to handle IPFS URIs” so user can change their mind later

(thx @aschmahmann for noticing that onboarding is especially confusing if user’s default browser is not the one with ipfs-companion)

[lidel]

This is a significant UX improvement, bumped a priority a bit.

ps. I suspect protocol handler does not work everywhere (eg. https://github.com/ipfs-shipyard/ipfs-desktop/issues/1549).

[jessicaschilling]

a separate window that loads the modal page

Confirmed this just means modal appears in its own window without Web UI furniture behind it: i.e., ignore grayed-out Web UI interface behind the modal in the mockup above. Can amend mockup if this is absolutely necessary, but this should be ready to work. Text (for copy-paste convenience) is as follows:

How would you like IFPS Desktop to open this ipfs://URI?

• In my default browser using a public gateway
• In my default browser using my local gateway
• In the Files screen
• In the Explore Screen

(checkbox) Remember this choice for all ipfs:// URIs

(buttons) Close / Continue

Note that the image in the modal is the standard stroke_link icon from ipfs-css.