Migrate native app from Tauri v1 to v2

[grMLEqomlkkU5Eeinz4brIrOVCUCkJuN]

Description

• Bump tauri and tauri-build to 2; split the v1 api-all surface into the plugins actually used (fs, dialog, updater, process)
• Convert tauri.conf.json to the v2 schema and add capabilities
• Port the frontend to the v2 plugin imports and the new fs, updater, and window APIs
• Drop window-shadows in favour of the built-in window shadow
• Pin tauri-runtime 2.10.1 and wry 0.54.0 to match the published tauri-runtime-wry 2.10.1; newer versions of either break the build
• Update CI to libwebkit2gtk-4.1-dev and the v2 signing environment variables

Motivation

Builds the desktop app against webkit2gtk-4.1 (in the official repos) instead of the removed webkit2gtk-4.0, so it no longer needs the old library compiled from source. (It is incredibly annoying to wait for legacy version with no precompile binary on my i3 6th gen machine, but I understand that everyone is busy. <3)

Additional Context

• Initially made for myself, but thought devs might be interested, thanks for making an editor dedicated to minecraft modding, I really loved this project.
• I also chose to target the main branch directly since the dev branch for some reason has a weird commit history, let me know if I should redo this part. Apologies in advance.

Thank you for your time <3

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[outercloudstudio]

Thanks for the pr :D We were planning on moving to V2 soon because of the many build issues / deprecation with V1, so this helps me out a lot.

Also yep, main branch is the most up to date right now, currently working on a better organization. Previously everything was pushed on dev, and then moved to main eventually, but I'm leaning towards most of development happening on a specific feature branch (if it would take multiple commits) and then bringing it to main without the dev branch.

[grMLEqomlkkU5Eeinz4brIrOVCUCkJuN]

Thanks for the pr :D We were planning on moving to V2 soon because of the many build issues / deprecation with V1, so this helps me out a lot.

Also yep, main branch is the most up to date right now, currently working on a better organization. Previously everything was pushed on dev, and then moved to main eventually, but I'm leaning towards most of development happening on a specific feature branch (if it would take multiple commits) and then bringing it to main without the dev branch.

No worries <3, most of the stuff here was actually taken care of tauri migrate, I only really resolved updated env vars and import paths.

@outercloudstudio when will this be merged? No rush, just curious as im thinking of adding other features and possibly resolving community issues once you are done.

[outercloudstudio]

I was planning on some time before the end of the week.