fix: recover release snapshot state

[Idddd]

Motivation

• A prior release run left the repository with a released (non-SNAPSHOT) version, causing subsequent release workflow runs to retry from a stale formal version and fail unpredictably.
• Add a fast, actionable preflight in the release workflow so interrupted releases are diagnosed clearly and do not proceed.

Description

• Bump the development version in gradle.properties to the next snapshot: set version=0.1.35-SNAPSHOT to recover the repository from a stale release state.
• Add a preflight step Verify snapshot version to .github/workflows/release.yml that checks gradle.properties contains a -SNAPSHOT version and fails with a clear Actions error if it does not.
• Keep the existing release command (./gradlew release -Prelease.useAutomaticVersion=true) unchanged and only gate it behind the new snapshot verification.

Testing

• Ran git diff --check and verified there were no whitespace/patch errors (passed).
• Validated the snapshot guard with version="$(sed -n 's/^version=//p' gradle.properties)" to confirm the current gradle.properties passes the new check (passed).
• Simulated a stale non-SNAPSHOT version=0.1.34 and confirmed the guard rejects it (passed).
• Parsed the modified workflow YAML with Ruby (YAML.load_file) to confirm the Verify snapshot version step exists and is syntactically valid (passed).
• Attempting to run ./gradlew --version in the local environment failed because the gradle/wrapper/gradle-wrapper.jar is stored via Git LFS and the LFS object is not available locally, and a local Gradle invocation failed to resolve a plugin artifact due to environment/network restrictions (environmental limitation documented).

---

Codex Task