Add LogQL support for Loki v3.1.0

[periklis]

Add support for LogQL features included in Loki between 2.9.8 and v3.1.0. Diff:

6df81db97 feat: Support negative numbers in LogQL (#13091)
4c88be0ef chore: update loki modules for 3.0 release (#12433)
36c703dae feat: add pattern match line filter (#12398)
cc941fe42 chore: refactor line filter MatchType (#12388)
60edfe000 Implement "or" statement in line filters (#8962)
6bced8345 [release-2.9.x] Revert "LogQL: Introduce `distinct` (#8662)" (#10358)
c030217e1 Revert "LogQL: Introduce `distinct` (#8662)" (#10356)

LogQL features implemented in our log api's parser:

• feat: Support negative numbers in LogQL grafana/loki#13091
• feat: add pattern match line filter grafana/loki#12398
• Implement "or" statement in line filters grafana/loki#8962

Refs: LOG-5761

/cc @JoaoBraveCoding @jotak

[JoaoBraveCoding]

Tested:

• negative numbers ✅
• "or" statement in line filters ✅
• patter match line filter 🚧

When testing I was able to get results with the following expression:

{ log_type="application" } !> "I <_>"| json

But using the inverse:

{ log_type="application" } |> "I <_>"| json

I would get: Parse error at line 1, col 30: syntax error: unexpected STRING

[periklis]

@JoaoBraveCoding The issue described with pattern line filters is truly on applicable with OCP's Log Console. Pending fixes for the console:

• Add support for pattern match/not-match line filters grafana/lezer-logql#63
• LOG-5761: Add support LogQL pattern line filters openshift/logging-view-plugin#200

Meanwhile limit testing to logcli please such as:

export LOKI_PUBLIC_URL=$(k -n openshift-logging get route lokistack-dev -o jsonpath="{.spec.host}")

logcli --tls-skip-verify --bearer-token="$(oc whoami -t)" --addr "https://${LOKI_PUBLIC_URL}/api/logs/v1/application" query '{ log_type="application" }  |> "I <_>"| json'