fix(test): filter out OTel internal metrics in opentelemetry-metrics ITs

[gnodet]

Summary

• OpenTelemetry 1.60+ exports internal SDK metrics (e.g. otel.sdk.metric_reader.collection.duration) via LoggingMetricExporter
• ManagedMessageHistoryAutoConfigIT and ExchangeEventNotifierAutoConfigIT assumed only Camel metrics would appear in the log output, causing assertion failures with OTel 1.60.1 (chore(deps): Bump opentelemetry-version from 1.59.0 to 1.60.1 #21827, chore(deps): Bump io.opentelemetry:opentelemetry-bom-alpha from 1.59.0-alpha to 1.60.1-alpha #21851)
• Filter out non-Camel metrics by checking for the camel. prefix before processing log records
• This is a proper fix — alternative to reverting OTel to 1.59 (Revert open telemetry to 1.59 #21881)

Test plan

• ManagedMessageHistoryAutoConfigIT passes with OTel 1.60.1
• ExchangeEventNotifierAutoConfigIT passes with OTel 1.60.1

[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.