Fix copy-paste error in camel-milo MiloClientConfiguration (found by OpenScanHub SAST)

[tedwon]

What

Fix a copy-paste error in MiloClientConfiguration where getMaxPendingPublishRequests() was called instead of getMaxResponseMessageSize() when configuring the OPC UA client's max response message size.

Why

The OPC UA client's maxResponseMessageSize is set to the value of maxPendingPublishRequests instead of maxResponseMessageSize. This applies the wrong value to the message size limit — for example, if maxPendingPublishRequests is 10, the max response size would be set to 10 bytes instead of the intended limit.

Fix

Change configuration.getMaxPendingPublishRequests() to configuration.getMaxResponseMessageSize() on line 464.

Found via static analysis (Coverity COPY_PASTE_ERROR checker).

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

🧪 CI tested the following changed modules:

• components/camel-milo

All tested modules (8 modules)

• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher :: Container
• Camel :: Milo
• Camel :: YAML DSL :: Validator
• Camel :: YAML DSL :: Validator Maven Plugin

---

⚙️ View full build and test results