Suggestions about Variant Feature

## Enhancements for the Variant Feature

For Chainforge 4.3.7 version:

First, I want to express my sincere appreciation for the Variant feature added to Prompt nodes. This addresses a critical pain point for Prompt Engineers who typically need to make numerous iterations of their prompts. This feature is exactly what I've been hoping for!

My current workflow involves developing prompts in promptmetheus.com and then running batch tests in ChainForge. I'm eager to migrate my entire prompt assembly process to ChainForge, and the Variant feature is a promising step in that direction.

I'd like to suggest two enhancements to make this feature even more powerful:

### 1. Named Variants with Tab Navigation

Currently, variants can only be switched using left/right buttons, which becomes cumbersome when working with multiple variants.


**Request:** Please consider adding:
- The ability to name each variant individually
- A tab-based interface at the top of the node to quickly switch between variants rather than cycling through them sequentially

Below is a screenshot of the promptmetheus, which they achieve this kind of design, you can refer as well:


### 2. Extend Variant Support to Text Fields Nodes

While the table functionality is useful for batch processing, there are many scenarios where I'm working with different groups of data rather than multiple data points within the same group.

For example, when testing a prompt about cities like:
What's the special food in {City_name}?

I might want to test with "Beijing" in one variant, "New York" in another, and "Tokyo" in a third.
Using a TabularDataNode for this requires running tests with all three cities at once, but sometimes I just want to test one city at a time with different prompt variants.

**Request:** Please consider extending the Variant feature to:
- Text Fields Nodes (highest priority)
- ItemsNode and TabularDataNode (if feasible in the future)
- Evaluator nodes (as a future enhancement)

This would allow for a more flexible testing approach during the prompt development phase, before moving to batch testing with tables.

Thank you for considering these suggestions, and again, thank you for developing such a valuable tool for the prompt engineering community!