fix: enum values instead of names in testset synthesizers

[lovets18]

Change
Using Enum.value instead of Enum.name

It seems that value (description) for QueryStyle is more logical than using names. The current name and value are almost identical, but this might change in the future

[greptile-apps]

Greptile Summary

This PR modifies the testset synthesizer components to use enum .value instead of .name when passing QueryLength and QueryStyle parameters to language model prompts. The change affects both single-hop and multi-hop query synthesizers in the ragas framework.

Specifically, the modification changes how enum parameters are passed to the prompt generation system:

• For QueryLength: Changes from passing uppercase names like 'LONG', 'MEDIUM', 'SHORT' to lowercase values like 'long', 'medium', 'short'
• For QueryStyle: Changes from passing programmatic identifiers like 'MISSPELLED', 'PERFECT_GRAMMAR' to descriptive phrases like 'Misspelled queries', 'Perfect grammar'

This change integrates with the broader testset generation system where synthesizers create scenarios and samples for evaluating LLM applications. The BaseScenario class contains QueryLength and QueryStyle enums that define query characteristics, and these synthesizers use these enums to generate appropriate test queries. By using the descriptive enum values, the system provides more meaningful context to the language models during query generation, which should improve the quality and accuracy of synthesized test data.

The change is applied consistently across both synthesizer types, indicating a deliberate architectural decision to standardize on using descriptive enum values throughout the query generation pipeline.

Confidence score: 4/5

• This change is relatively safe as it only modifies how enum values are passed to prompts without changing core logic
• The modification improves prompt clarity for language models, which should enhance generation quality
• Both affected files need attention to ensure the enum values are properly defined and consistent with the new usage pattern

_{2 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[anistark]

Thanks for the fix @lovets18 Could you please edit the commit msg to something more meaningful?

[lovets18]

@anistark Thanks for the feedback! Updated the commit message to describe the change

[anistark]

Thanks @lovets18 🎉