Add UI validation for EnderGPT conflicts between prompt instructions and system filters

Add a validation mechanism that detects potential conflicts between the user prompt and the system filters applied to the request before it is submitted for processing.

Currently, the prompt and system filters are processed independently. This allows users to create requests where the prompt defines one data scope while the selected filters restrict the data to a conflicting scope.

Example:

Prompt:

Analyze only conversations from August 2026. Do not use data from September or the current month.

Applied system filter:

Time range: Current month

In this case, the request becomes logically conflicting and may return no relevant data or produce an incorrect result.

Required Changes

Before the request is submitted, the UI should check for obvious conflicts between:

• date ranges mentioned in the prompt and selected time filters;

• explicit exclusions in the prompt and active filters;

• other supported prompt conditions that directly contradict selected system filters.

If a conflict is detected, the conflicting elements should be visually highlighted and the user should receive a warning before running the request.

Expected Behavior

The warning should clearly indicate which prompt condition conflicts with which system filter.

Example:

Potential conflict detected: the prompt requests data from August 2026, while the active time filter is set to Current month.

The user should be able to review and correct either the prompt or the filter before submitting the request.

The validation should focus on clear contradictions and should not block valid requests based on uncertain interpretation.

Acceptance Criteria

1. Obvious conflicts between prompt conditions and supported system filters are detected before submission.

2. Conflicting prompt text and/or filters are visually highlighted.

3. The UI explains the detected conflict in a clear warning.

4. The user can adjust the prompt or filters before running the request.

5. Existing request flow remains unchanged when no conflict is detected.