Complete Snyk fix with automated fallback version management

[fdevans]

What It Does:
Gets the release version from the tag
Switches to main branch temporarily
Updates gradle.properties with the new fallback version
Commits and pushes the change to main (with [skip ci] to avoid triggering other workflows)
Switches back to the tag to continue the release process
Benefits:
✅ Automatic maintenance: No manual version updates needed
✅ Always current: Fallback version matches the latest release
✅ Safe: Only updates when there are actual changes
✅ Non-disruptive: Uses [skip ci] to avoid triggering other workflows
✅ Reliable: Handles the case where the update isn't needed
How It Works:
When you create a new tag/release (e.g., 1.2.0)
The workflow runs and updates gradle.properties in the main branch with fallback.version=1.2.0
Future Snyk scans will use this current version instead of an outdated one
No manual maintenance required!

[Copilot]

Pull Request Overview

This PR implements automated fallback version management in the release workflow to ensure Snyk scans use current version information instead of outdated fallback versions.

• Adds a gradle.properties file with a fallback version for CI environments where Git history is unavailable
• Modifies the release workflow to automatically update the fallback version in the main branch during releases
• Implements safe updating logic that only commits changes when needed and uses [skip ci] to prevent workflow loops

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File	Description
gradle.properties	Adds fallback version configuration for CI environments
.github/workflows/release.yml	Implements automated fallback version updates during release process

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}