CAMEL-23149: Add TLS configuration options to camel-iggy

[gnodet]

Summary

• Add tlsEnabled (boolean, default false) and tlsCertificatePath (String) configuration options to IggyConfiguration
• Update IggyClientFactory to apply TLS settings when building TCP and HTTP iggy clients via enableTls() and tlsCertificate(path) builder methods
• Propagate TLS parameters through IggyClientConnectionPool, IggyProducer, and IggyConsumer
• Add unit tests for TLS configuration defaults, setters, copy behavior, and endpoint URI parsing

Test plan

• Unit tests pass (IggyConfigurationTest with 5 tests covering defaults, setters, copy, and endpoint URI parsing)
• Integration tests with TLS-enabled Iggy server (requires TLS-configured Iggy instance)

[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 build-all, build-dependents, 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.

[oscerd]

I think we should expose SSLContextParameters as configuration. This is for PQC.

[gnodet]

@oscerd Good point — and this is already covered in this PR! SSLContextParameters is exposed as a configuration option (along with useGlobalSslContextParameters), which gives full control over TLS configuration including PQC cipher suites. It takes precedence over tlsEnabled and tlsCertificatePath when configured.