Java: Make jedis-compatibility a pure-Java JAR with no-classifier support

[affonsov]

Summary

Make valkey-glide-jedis-compatibility a pure-Java JAR by removing native library bundling, and publish a no-classifier variant so users no longer need to specify a platform classifier.

Issue link

This Pull Request is linked to issue:
Closes <Issue #>

Features / Behaviour Changes

Before: Users had to specify a platform classifier when depending on valkey-glide-jedis-compatibility:

<classifier>linux-x86_64</classifier>

After: No classifier needed. The uber JAR is resolved transitively via the POM:

<dependency>
    <groupId>io.valkey</groupId>
    <artifactId>valkey-glide-jedis-compatibility</artifactId>
    <version>2.3.0</version>
</dependency>

Implementation

java/jedis-compatibility/build.gradle:

• Removed the copyNativeLib task and all its dependsOn references — the JAR no longer bundles native libraries
• Added JEDIS_NO_CLASSIFIER_BUILD env var support to the jar block:
  • "true" → no classifier (for the new no-classifier JAR)
  • Otherwise → existing classifier logic (musl or osdetector)

.github/workflows/java-cd.yml:

• Added 3 steps to the create-uber-jar job:
  1. Build jedis-compatibility with JEDIS_NO_CLASSIFIER_BUILD=true (skips Rust, reuses already-compiled client)
  2. Bundle the Maven local output into jedis-bundle-no-classifier.jar
  3. Upload as jedis-no-classifier artifact
• The publish job needs no changes — existing glob patterns pick up the new artifact automatically

Limitations

• Classifier JARs are still published during the transition period (they now contain pure Java, same as the no-classifier JAR)
• Users who exclude the transitive valkey-glide dependency will get UnsatisfiedLinkError at runtime

Testing

• YAML syntax validated for java-cd.yml
• Verified publish job glob patterns handle the new artifact
• Verified POM consistency across classifier and no-classifier builds

Checklist

Before submitting the PR make sure the following are checked:

• This Pull Request is related to one issue.
• Commit message has a detailed description of what changed and why.
• Tests are added or updated.
• CHANGELOG.md and documentation files are updated.
• Linters have been run (make *-lint targets) and Prettier has been run (make prettier-fix).
• Destination branch is correct - main or release
• Create merge commit if merging release branch into main, squash otherwise.