Add GraalVM native binary releases for Linux and macOS

[Copilot]

Plan: Add GraalVM Native Binary Releases ✅

• Configure Maven for GraalVM native-image builds
  • Add native-image-maven-plugin to pom.xml
  • Add necessary GraalVM native-image configuration
  • Configure JavaFX support for native-image
• Update release-builds.yml workflow
  • Add native-image build steps for Linux
  • Add native-image build steps for macOS
  • Package native binaries with FFmpeg
  • Upload native binary packages to release
• Update CI workflow to test native builds
  • Add native-image build verification for Linux
  • Add native-image build verification for macOS
• Add launcher script for native binaries
• Update documentation
  • Update README with native binary info
  • Add build instructions
• Address code review feedback
  • Remove duplicate build args from pom.xml
  • Use clean target before native builds in CI
  • Add comments about FFmpeg URL considerations
• Security scan completed (no issues found)
• Fix CI build failure
  • Changed ControlsFX initialization from build-time to runtime to avoid JavaFX toolkit dependency issues

Summary

Fixed native-image build failure caused by ControlsFX RangeSlider initialization. The issue was that ControlsFX classes were being initialized at build-time but they depend on JavaFX toolkit which can only be initialized at runtime. Changed configuration to initialize ControlsFX at runtime along with JavaFX platform.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Binary Releases</issue_title>
<issue_description>The release builds created in #1 are simply jar archives and require java. We also need binary releases bundled and ready to execute on each platform using the GraalVM action builder. Review the flow and make sure BINARIES are produced by the release action.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Binary Releases #3

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[lmangani]

@copilot CI builds are failing https://github.com/katamini/SpriteLab/actions/runs/21248346717/job/61143603572
Review the build process and correct the blocking issue.

[Copilot]

@copilot CI builds are failing https://github.com/katamini/SpriteLab/actions/runs/21248346717/job/61143603572
Review the build process and correct the blocking issue.

Fixed the build failure in commit 9eef1ea. The issue was that ControlsFX classes were being initialized at build-time but depend on the JavaFX toolkit which can only be initialized at runtime. Changed the configuration to initialize ControlsFX at runtime instead.