Create fedora rpms build artifacts for release

[SidShetye]

Describe Your Changes

This change creates rpm build artifacts for Fedora and related distros.

Why rpm ?

This was briefly raised at #6115 (I was absent there, just found this project a couple of hours back) but that was closed as providing flatpak as an alternative. However flatpak's sandbox and portals actually get in the way when trying to manage various custom llamas and models, while a native rpm is able to work very easily with the existing model and runtime libraries on a system.

Example:

In ~/.var/app/ai.jan.Jan/data/Jan/data/llamacpp/models/some-model.gguf/model.yml you might have

mmproj_path: /run/user/1000/doc/992d4590/mmproj-model-f16.gguf 
model_path: /run/user/1000/doc/ea87324/model.gguf 

Those entries are very opaque, leading to a poor experience. Plus those /run/user/1000/doc/<id>/ entries are ephemeral mount points created by the xdg-document-portal service, so they are on their own lifecycle.

All said and done, the native deb or rpm application run is great for power users on Linux.

Other considerations

I kept the commit to have the binary called jan as opposed to Jan by default as a separate commit to allow easy picking. I personally think a Jan binary is weird on linux but so you guys can decide :) !

[Vanalite]

Please keep the commit of changing Jan to jan to another PR. Plus, you're modifying it on tauri config, which will impact all other platforms, not just for linux.

[SuperCowProducts]

Hey there, wish I had remembered to search through PRs to find this before submitting an issue and figuring it out on my own, but I got the job done with this little hack: #4543 (comment)

Out of curiosity, is this of any use, or would the script have found the libraries for Fedora's repos automatically once you added rpm to the list visible in the diff?

[tokamak-pm]

Code Review

Summary

Adds "rpm" to the Tauri bundle targets in tauri.linux.conf.json to enable Fedora RPM build artifacts. Minimal one-line config change.

Key Findings

• The config change is valid for Tauri's bundle configuration.
• No CI pipeline — RPM builds require rpmbuild tooling. If the Linux CI runner lacks these tools, builds will fail.
• No install validation — No evidence the resulting .rpm was tested on a Fedora system. Tauri's RPM support has had historical packaging issues (desktop entries, icon paths, dependencies).
• No documentation update — No update to the download table in README or release docs.
• Commit history is clean (reverted an unrelated change).

Recommendation: fix needed

Add a CI step verifying RPM build success, test install/run on Fedora, and update release documentation. At minimum, document RPM as experimental.