Add official macOS Intel .dmg release build

[merajmunshiofficial]

Hi, the current releases provide Windows setup files, but macOS users currently need to build from source.

I tested packaging Proxima locally on an Intel Mac using electron-builder and was able to produce a working x64 macOS app/ZIP.

It would be useful to add an official macOS Intel release artifact, ideally a .dmg, so Mac users can install Proxima without running npm commands.

Suggested package scripts:

"dist": "electron-builder --mac --x64",
"dist:mac": "electron-builder --mac --x64",
"dist:dmg": "electron-builder --mac dmg --x64"
Notes:
- The app can be built as macOS x64 for Intel Macs.
- The existing `assets/proxima-icon.png` can be used as the app icon.
- For public distribution, signing/notarization may be needed to avoid macOS security warnings.

I can open a PR with the packaging changes if maintainers are open to supporting macOS release artifacts.

[daveCode-dot]

Great scoping! Before accepting the PR, verify:

1. Apple Silicon support: Your build targets x64 Intel. If maintainers want ARM64 (Apple Silicon M1+), electron-builder supports --mac universal to create fat binaries covering both architectures. That's the standard for modern macOS releases.

2. Code signing: You mentioned signing/notarization. Per Apple's requirements (2024+), any macOS app distributed outside App Store needs:

   • Code signature with Developer ID certificate
   • Notarization via altool or Transporter (15-30 min turnaround)

   This requires a paid Apple Developer account (/yr). Check if maintainers have capacity to manage this.

3. CI/CD: Building .dmg on each release requires macOS runners in CI/CD. GitHub Actions supports macOS runners but costs ~/bin/zsh.14/min. Factor this into release automation.

Suggestion: Scope the PR to electron-builder config only (x64 + universal builds), but defer signing/notarization decision to maintainers. That lets you contribute the build setup, and they decide on the infrastructure cost/benefit.