Alerting: No Alert for result value zero

### What happened? We use the expression `up{job="kubelet",metrics_path="/metrics"}==0` to monitor whether the target is down, but Grafana Alerting applies special handling to the value of 0. ref: ``` apiVersion: 1 groups: - orgId: 1 name: test folder: test interval: 10s rules: - uid: ff98cool4z5s0e title: kubelet_Down_10s condition: A data: - refId: A relativeTimeRange: from: 600 to: 0 datasourceUid: xxxxxx model: editorMode: code expr: up{job="kubelet",metrics_path="/metrics"}==0 instant: true intervalMs: 1000 legendFormat: __auto maxDataPoints: 43200 range: false refId: A noDataState: OK execErrState: Error for: 10s annotations: description: kubelet_Down:{{$labels.node}},instance:{{$labels.instance}}！ summary: sae{{$labels.sae_cluster}}k8s_kubelet_Down:{{$labels.node}}！ value: '{{ $values.A.Value }}' isPaused: false notification_settings: receiver: test ``` ### What did you expect to happen? 1. value == nil , NoData 2. *value == [], NoData 3. *value != [], Alerting ### Did this work before? When *value is zero, Setting Narmal, No Alerting. https://github.com/grafana/grafana/blob/844a7332b9032fed016e9aaf7076eebbf2f6460c/pkg/services/ngalert/eval/eval.go#L805-L812 ### How do we reproduce it? 1. result == nil , NoData 2. *result == [], NoData 3. *ressult has values, Alerting ### Is the bug inside a dashboard panel? _No response_ ### Environment (with versions)? Grafana: v12.3.1 OS: Mac OS Browser: chorme ### Grafana platform? Docker ### Datasource(s)? _No response_