[FEATURE] Requirements for experience and experimental features

### 📋 Please ensure that:

- [ ] I have searched existing issues to avoid duplicates
- [ ] I have provided a clear problem statement and solution
- [ ] I understand this is a feature request and not a bug report
- [ ] I am willing to help implement this feature if needed
- [ ] I have submitted this feature request in English (otherwise it will not be processed)

### 🎯 Problem Statement

1.Is it possible to support pausing or stopping the experiment? Users can pause/stop the experiment during the experiment and modify the experiment properties later.

2.During the experiment, some evaluation sets failed to run, with the failure reason displayed as "Server internal error." Could you provide more detailed information on the cause?

For functions like creating prompts and evaluators, when encountering duplicate resources, the prompts for the reason could be more detailed.

3.When uploading a test set, you should provide a file data template

### 💡 Proposed Solution

1.Is it possible to support pausing or stopping the experiment? Users can pause/stop the experiment during the experiment and modify the experiment properties later.

2.During the experiment, some evaluation sets failed to run, with the failure reason displayed as "Server internal error." Could you provide more detailed information on the cause?

For functions like creating prompts and evaluators, when encountering duplicate resources, the prompts for the reason could be more detailed.

3.When uploading a test set, you should provide a file data template

### 📋 Use Cases

1.Is it possible to support pausing or stopping the experiment? Users can pause/stop the experiment during the experiment and modify the experiment properties later.

2.During the experiment, some evaluation sets failed to run, with the failure reason displayed as "Server internal error." Could you provide more detailed information on the cause?

For functions like creating prompts and evaluators, when encountering duplicate resources, the prompts for the reason could be more detailed.

3.When uploading a test set, you should provide a file data template

### ⚡ Priority

None

### 🔧 Component

None

### 🔄 Alternatives Considered

_No response_

### 🎨 Mockups/Designs

_No response_

### ⚙️ Technical Details

_No response_

### ✅ Acceptance Criteria

_No response_

### 📝 Additional Context

_No response_