Not-equals of two lists is not working in `requires:`

### Bug Description

Given this resource:
```yaml
case: GLMark2Xwayland.fullscreen
xwayland: True
hosted: False

case: GLMark2Xwayland.windowed
xwayland: True
hosted: False

case: HostedGLMark2Wayland.fullscreen
xwayland: False
hosted: True

case: HostedGLMark2Wayland.windowed
xwayland: False
hosted: True
```

And this manifest:
```ini
[manifest]
io.mir-server::skip_xwayland_tests = true
```

With a `==` this correctly skips the cases that don't match.
```plain
requires:
[manifest.skip_xwayland_tests, "{xwayland}"] == ["True", "True"]

# ...

☑ : Run Mir performance test case: GLMark2Xwayland.fullscreen
☑ : Run Mir performance test case: GLMark2Xwayland.windowed
☐ : Run Mir performance test case: HostedGLMark2Wayland.fullscreen
☐ : Run Mir performance test case: HostedGLMark2Wayland.windowed
```

But flip the condition and they all run…

```plain
requires:
[manifest.skip_xwayland_tests, "{xwayland}"] != ["True", "True"]

# ...

☑ : Run Mir performance test case: GLMark2Wayland.fullscreen
☑ : Run Mir performance test case: GLMark2Wayland.windowed
☑ : Run Mir performance test case: GLMark2Xwayland.fullscreen
☑ : Run Mir performance test case: GLMark2Xwayland.windowed
```

Unless I'm missing something weird with requires…

### To Reproduce

See above

### Environment

N/A

### Relevant log output

_No response_

### Additional context

_No response_

Start by reproducing the manifest and requires expressions shown in the issue, then trace the requires expression evaluation that handles list comparisons. Confirm the behavior for both == and != with the two lists, and consider the work done when the != form filters the same cases as the inverted == condition.

Written by the indexing model from the issue text.