Description of problem:

Unable to filter logs by severity since according to OTEL semantic conventions 'log_level' is included as 'severity_text but console filters still use the viaq 'level' label.

According to the Acceptance criteria for EPIC https://issues.redhat.com/browse/LOG-5637

a) Given the cluster administrator searching for logs in the Log Console given using OpenTelemetry Semantic Conventions to name labels and filter in LogQL, then LokiStack returns log records matching those.
b) Given the cluster administrator searching for logs by using one Log Console UI filters (currently severity/namespaces/pod/containers/tenant) , then LokiStack returns log records matching those by using OpenTelemetry Semantic Conventions to name labels and filter in LogQL.

As per OTEL convention, severity_text is same as Log_level and should be used for severity. Reference: https://opentelemetry.io/docs/concepts/signals/logs/#log-record

Version: Logging 6.1

How reproducible: Always

Steps to Reproduce:
a) Deploy Loki and CLO v6.1
b) Forward Logs to LokiStack using Otel dataModel.
c) Query for logs on console and include severity of logs.

Actual results: Correct/matching results are not displayed since 'level' is not a OTEL semantic convention.

Expected results: Console should include the correct OTEL semantic label when filtering out logs by severity.

Additional info:

Attached screenshots of console. As one can see, for Infra logs, the severity 'info' cannot be filtered since there is no field as 'level' but can query when 'severity_text' is included.

CLF Spec:

spec:
  managementState: Managed
  outputs:
    - lokiStack:
        authentication:
          token:
            from: serviceAccount
        dataModel: Otel
        target:
          name: lokistack-dev
          namespace: openshift-logging
        tuning:
          compression: none
      name: lokistack-otlp
      tls:
        ca:
          configMapName: openshift-service-ca.crt
          key: service-ca.crt
      type: lokiStack
  pipelines:
    - inputRefs:
        - application
        - infrastructure
        - audit
      name: my-pipeline
      outputRefs:
        - lokistack-otlp
  serviceAccount:
    name: loki-otlp