Fix log-format multiline syntax causing parsing errors

- Convert multiline log-format to single line to avoid quote parsing issues
- Maintains all logging fields: client_ip, threat_score, glitches, h2_streams, user_agent, threat_level
- Resolves HAProxy 3.0.11 configuration parsing errors

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

templates/hap_listener.tpl

@@ -214,13 +214,7 @@ frontend web
     http-request capture var(txn.threat_score) len 10
 
     # Enhanced logging format with glitch information
-    log-format "%{+json}o \
-        %(client_ip)[var(txn.real_ip)] \
-        %(threat_score)[var(txn.threat_score)] \
-        %(glitches)[fc_glitches] \
-        %(h2_streams)[fc_nb_streams] \
-        %(user_agent)[capture.req.hdr(1)] \
-        %(threat_level)[res.hdr(X-Threat-Level)]"
+    log-format "%{+json}o %(client_ip)[var(txn.real_ip)] %(threat_score)[var(txn.threat_score)] %(glitches)[fc_glitches] %(h2_streams)[fc_nb_streams] %(user_agent)[capture.req.hdr(1)] %(threat_level)[res.hdr(X-Threat-Level)]"
 
     # Set log level based on threat score
     http-request set-log-level info if { var(txn.threat_score) -m int lt 20 }