GCVCALLP-3095: Parallel MI via multiple httpd listeners w/ async workers

[benceszigeti]

• Per-listener worker count—each HTTP listener can run multiple workers, so MI requests are handled in parallel instead of serially by a single worker.
• Multiple listeners—define several HTTP endpoints, each with its own worker pool, to isolate critical MI traffic from general traffic.

Listeners are configured with [name]-prefixed modparam values and created on demand (no fixed limit). Values without a prefix target the default listener, so existing configs keep working.

Example new config

#// General MI listener
modparam("httpd", "ip", "[default]127.0.0.1")
modparam("httpd", "port", "[default]8888")
modparam("httpd", "receive_buf_size", "[default]65536")
modparam("httpd", "workers", "[default]8")

#// Critical MI listener
modparam("httpd", "ip", "[critical]127.0.0.1")
modparam("httpd", "port", "[critical]8889")
modparam("httpd", "receive_buf_size", "[critical]65536")
modparam("httpd", "workers", "[critical]2")

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 66 complexity

Metric	Results
Complexity	66

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}