Upgrade Tauri from v1 to v2

[ndpm13]

Description

The other PR brings way too many changes and adds unnecessary deps. I've tested this on a Void Linux system since I can't run mainline cinny-desktop on it (due to some libsoup/javascriptcore errors).

Fixes #398

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[niklaskorz]

"Enable desktop notifications" does not seem to do anything, and I get 401 Unauthorized for all media requests to my homeserver. Besides that, appears to work fine!

[ndpm13]

"Enable desktop notifications" does not seem to do anything

I didn't notice that, it shouldn't be hard to fix. However, I have no idea how to work around the media error without patching the Cinny core itself 😅

[niklaskorz]

However, I have no idea how to work around the media error without patching the Cinny core itself 😅

The cinny issue suggests this to be related to the service worker not running in a secure context, see the comments here: cinnyapp/cinny#2274

However, evaluating window.isSecureContext in the Cinny Tauri console gives me true. 🤔

Edit:

Running await navigator.serviceWorker.getRegistrations() in the console shows that no service worker is registered! This might explain both the desktop notifications issue as well as the media authorization issues.

[niklaskorz]

It looks like this expects an object now, instead of a string:

https://v2.tauri.app/security/csp/

[ndpm13]

...Notifications aren't working correctly for me in the browser, not only in Tauri. Any ideas what's that about?

[nyabinary]

How long until do you think this will take to land? Because we don't want to maintain this as a patch if possible in nixpkgs.