Update Valkey GLIDE dependency to Uber Jar

[Aryex]

Overview

• Updated the GLIDE dependency to using the uber jar. Related documentations has been updated.
• Also verified that the zset ordering issue noted in ZSetOperations range*WithScores do not maintain set ordering with a Glide cluster connection #36 has been fixed. Regression tests were added.

Related Issues

Closes #36
Related #81

Checklist

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

[jeremyprime]

Did you ensure all examples run after upgrade? Also performance module (even though it is going to be deprecated and removed in favor of resp-bench at some point)?

[jeremyprime]

One other area to check is docs/ folder which is deployed to spring.valkey.io. At a minimum I think drivers.md there could be updated (just remove classifier and update version in example, so very simple change).