feat(core): allow config app dir override

[Legend-Master]

Reference: #3109

Closes tauri-apps/plugins-workspace#3020
We could still do tauri-apps/plugins-workspace#3022 by changing filename to take a path (which can be relative)

[github-actions]

Package Changes Through 58bb684

There are 9 changes which include tauri with minor, tauri-macos-sign with patch, tauri-build with patch, tauri-bundler with patch, tauri-cli with patch, @tauri-apps/cli with patch, tauri-runtime-wry with minor, tauri-runtime with minor, tauri-utils with minor

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
tauri-utils	2.8.3	2.9.0
tauri-macos-sign	2.3.3	2.3.4
tauri-bundler	2.8.1	2.8.2
tauri-runtime	2.10.1	2.11.0
tauri-runtime-wry	2.10.1	2.11.0
tauri-codegen	2.5.5	2.5.6
tauri-macros	2.5.5	2.5.6
tauri-plugin	2.5.4	2.5.5
tauri-build	2.5.6	2.5.7
tauri	2.10.3	2.11.0
@tauri-apps/cli	2.10.1	2.10.2
tauri-cli	2.10.1	2.10.2

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[Legend-Master]

Very much open to suggestion on those paths, and we could document them once settled

[FabianLars]

This either needs to be windows only or have more warnings. Once you package the app on Linux and macOS most paths won't work anymore while on Windows they'd still work (on perUser installs).

Speaking about paths, would it make sense to still resolve the $DESKTOP etc variables (except the APP ones of course) ?

For Linux another one like $APPIMAGE or simply resolving the path relative to the APPIMAGE env var instead of current_exe would help as well since appimages are in lines with the portable app idea here, the current_exe is just a temp read-only path

[Legend-Master]

Once you package the app on Linux and macOS most paths won't work anymore while on Windows they'd still work (on perUser installs).

So my original idea was to only use this in non-packaged environment like portable apps and during debugging (in target directory), but I wasn't sure what name to use here and just went with this, we could expand the documentations of course

Speaking about paths, would it make sense to still resolve the $DESKTOP etc variables (except the APP ones of course) ?

Most of the paths still need to work I think, people might want to access those directories not just for storing their own data?

For Linux another one like $APPIMAGE or simply resolving the path relative to the APPIMAGE env var instead of current_exe would help as well since appimages are in lines with the portable app idea here, the current_exe is just a temp read-only path

Nice call, I'll change it to use current_binary here instead

[FabianLars]

Most of the paths still need to work I think, people might want to access those directories not just for storing their own data?

I meant in the new path config, so you could say your override should be somewhere on the Desktop or in the Documents dir.

Nice call, I'll change it to use current_binary here instead

totally forgot that's a thing x)

[Legend-Master]

I meant in the new path config, so you could say your override should be somewhere on the Desktop or in the Documents dir.

Ah I see what you mean now, good idea I guess