make max inflight warning global to all pipelines

[jsvd]

- pipeline.id: test_01
  config.string: "input { heartbeat {} } filter { sleep { time => 1 } } output { stdout { codec => dots } }"
- pipeline.id: test_02
  config.string: "input { heartbeat {} } filter { sleep { time => 1 } } output { stdout { codec => dots } }"
- pipeline.id: test_03
  config.string: "input { heartbeat {} } filter { sleep { time => 1 } } output { stdout { codec => dots } }"

~/elastic/logstash improve_max_inflight_warning ❯ bin/logstash -r -b 125 --debug | grep resource                 
[2024-10-24T11:44:44,941][DEBUG][logstash.pipelineresourceusagevalidator] For a baseline of 2KB events, the maximum heap memory consumed across 3 pipelines may reach up to 0.72% of the entire heap (more if the events are bigger).

~/elastic/logstash improve_max_inflight_warning ❯ bin/logstash -r -b 12500 --debug | grep resource
[2024-10-24T11:45:13,008][WARN ][logstash.pipelineresourceusagevalidator] For a baseline of 2KB events, the maximum heap memory consumed across 3 pipelines may reach up to 71.53% of the entire heap (more if the events are bigger). The recommended percentage is less than 10%. Consider reducing the number of pipelines, or the batch size and worker count per pipeline.

closes #8622

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: b3c60be

Failed CI Steps

• 🥼 Integration Tests / part 1
• 🥼 Integration Tests / part 2

History

• 💛 Build #1749 was flaky e92253a
• 💔 Build #1748 failed 4971334