Plan to fix workflow for JAR generation and release upload

• Analyze existing workflow and build configuration
• Verify that Maven build successfully creates JAR
• Update workflow JDK version from 11 to 17 (matching pom.xml requirement)
• Add workflow trigger for release tags
• Add step to upload JAR as artifact in CI workflow
• Add step to upload JAR to GitHub Releases on tag push
• Add .gitignore to exclude build artifacts
• Test the workflow changes
• Add documentation

Summary of Changes:

1. Fixed maven.yml workflow:

   • Updated JDK version from 11 to 17 (matches pom.xml requirement)
   • Added step to upload JAR as workflow artifact after build
   • This allows JAR files to be downloaded from CI runs

2. Created release.yml workflow:

   • Triggers on version tags (v*)
   • Builds the project with Maven
   • Automatically creates GitHub Release
   • Uploads JAR file to the release
   • Generates release notes automatically

3. Added .gitignore:

   • Excludes target/ directory (Maven build artifacts)
   • Excludes IDE files (.idea/, *.iml)
   • Excludes OS-specific files

4. Updated README.md:

   • Added download instructions
   • Added running instructions
   • Listed available commands
   • Added build instructions
   • Referenced release documentation

5. Created RELEASE.md:

   • Documents the release process
   • Explains how to create a new release with tags
   • Provides JAR file details

How to use:

• Push to main branch: CI workflow builds and uploads JAR as artifact
• Push a version tag (e.g., git tag v1.0.0 && git push origin v1.0.0): Creates a GitHub Release with the JAR attached

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