bug: Different installation paths between Windows Store version (MSI) and GitHub release version (EXE)

[louis-jan]

Description

Jan uses different installation paths depending on the installation method on Windows. The Windows Store version (MSI installer) and the GitHub release version (EXE installer) install to different locations, creating inconsistency across installation methods.

Steps to Reproduce

1. Install Jan using the Windows Store version (MSI installer)
2. Note the installation path
3. Uninstall and install Jan using the GitHub release version (EXE installer)
4. Note the installation path differs from the MSI version

Expected Behavior

Installation paths should be consistent across different installation methods, or the differences should be clearly documented to help users locate their Jan installation regardless of the method used.

Actual Behavior

Different installation paths are used depending on whether Jan is installed via:

• Windows Store version (MSI installer)
• GitHub release version (EXE installer)

Impact

This inconsistency may cause:

• User confusion when trying to locate Jan files or configuration
• Issues for users switching between installation methods
• Problems for tools, scripts, or automation that need to locate the Jan installation
• Difficulty in providing support instructions that work for all users

Additional Context

Having consistent installation paths across installation methods would improve user experience and reduce potential compatibility issues.

[Minh141120]

For now, I'll temporarily remove .msi on the github release, delegate this to 0.7.1 to dive deeper

[github-actions]

Found 2 possible duplicate issues:

1. feat: Jan Installer for Windows can choose folder path to install on #6440
2. chore: flexible installation path for windows installer #5538

---