Describe the Bug

When accessing /cool/getMetrics some of the metrics seem to be misformatted (missing white space between key and value).
See example below.

The strange thing is, not all metrics are affected but this formatting error in a single line will break parsing in prometheus.

Error message in prometheus:

Error scraping target: expected value after metric, got "\n" ("INVALID") while parsing: "kit_thread_count_total2\n"

Steps to Reproduce

1. Add example.com/cool/getMetrics to prometheus as metrics endpoint
2. Receive error messages about failed parsing because of invalid metrics value ("\n")

Alternative Steps to Reproduce

1. access metrics-url with browser or curl and notice missing white space in some lines.

Expected Behavior

metrics line should look like this:

kit_thread_count_total 2

Actual Behavior

line looks like this:

kit_thread_count_total2

Server

• Coolwsd version: 25.04.2.2 (git hash: 636e10a2b1)
• Collabora Officeversion: 25.04.2.2 (git hash: b678ed7469)
• OS and version: Archlinux
• Prometheus version: 3.3.1