Add commands flags based on static map

[uglide]

Introduces command flags to simplify command routing.

[Copilot]

Pull Request Overview

This PR introduces a command flags feature to the Jedis library by adding a static registry that maps Redis command names to their flags. The implementation retrieves command metadata from a Redis server and automatically generates flag mappings.

• Adds a code generator that connects to Redis servers to extract command metadata and generate flag mappings
• Implements a static command flags registry in CommandObject.java with comprehensive command coverage
• Provides a getFlags() method for runtime flag lookup with optimized memory usage through shared EnumSet instances

Reviewed Changes

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

File	Description
src/test/java/redis/clients/jedis/codegen/README.md	Documentation for the command flags registry generator tool
src/test/java/redis/clients/jedis/codegen/CommandFlagsRegistryGenerator.java	Code generator that retrieves Redis command metadata and updates the static registry
src/main/java/redis/clients/jedis/CommandObject.java	Core implementation with CommandFlag enum, static registry, and getFlags() method
pom.xml	Maven configuration to exclude code generators from test execution

---

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

[github-actions]

Test Results

   280 files  ±0    280 suites  ±0   11m 35s ⏱️ +10s
10 188 tests ±0  9 123 ✅ ±0  1 065 💤 ±0  0 ❌ ±0 
 2 703 runs  ±0  2 703 ✅ ±0      0 💤 ±0  0 ❌ ±0 

Results for commit 879cb0b. ± Comparison against base commit e7bf717.

♻️ This comment has been updated with latest results.

[ggivo]

Looks good.

For better traceability, I would suggest placing the generated code in a dedicated file.
Additionally, wrapping command metadata in in an interface (CommandMetadataRegistry.getFlag()) and providing it as an configurabel instance within CommandObject would be beneficial. The auto-generated registry can serve as the default, but users could replace it with a custom implementation if needed — for example, dynamically loading it from the server or providing a user-defined version.

[atakavci]

Adding the version of server - the generator running against- as part of generated content would be nice as well.

[atakavci]

lets not do this and put everything into a seperate completely auto-generate class like CommandFlagRegistry or some provider class,, and use generated content at once without need of regex or any other searching/parsing. Then just consume it from CommandObject as needed.

[uglide]

done