Support filtering workflow execution history by run status (Success / Failure / Partial success)

### Self Checks

- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones.
- [x] I confirm that I am using English to submit this report, otherwise it will be closed.
- [x] Please do not modify this template :) and fill in all the required fields.

### 1. Is this request related to a challenge you're experiencing? Tell me about your story.

I am using Dify workflow in production. When checking workflow execution logs, there is **no status filter** on the execution history page.
I cannot quickly filter only the `Failure` runs.

Every day there are a large number of workflow executions. I have to manually flip pages and look through all successful records one by one to find failed cases, which is very inefficient for troubleshooting failure issues and calculating failure rate.

I hope to add a dropdown status filter for workflow execution logs. The filter options can be:

- All
- Success
- Failure
- Partial success

The filter should work together with existing time range and keyword search.
The `status` field is already stored in database, this only requires frontend filter component and corresponding API query parameter, no database schema change needed.

### 2. Additional context or comments

Self-hosted Dify. This feature will greatly help daily operation, workflow stability inspection and batch failure review.

### 3. Can you help us with this feature?

- [ ] I am interested in contributing to this feature.

Start at the workflow execution history page and inspect how its existing time-range and keyword filters build the API request. Add status options for All, Success, Failure, and Partial success, ensuring status combines with the existing filters; done means the history list returns only matching runs without a database schema change.

Written by the indexing model from the issue text.