CAMEL-23615: Add getLastExchangeFailureHandledTimestamp() to management API and dev consoles

[davsclaus]

Summary

• Adds getLastExchangeFailureHandledTimestamp() to ManagedPerformanceCounterMBean — tracks when the last handled failure occurred (e.g. routed to dead letter channel)
• Implementation in ManagedPerformanceCounter sets the timestamp alongside the existing failuresHandled counter increment in completedExchange()
• Includes the new timestamp in dumpStatsAsXml() and statsAsJSon() output
• Added to all dev consoles: Route, RouteGroup, Processor, Consumer, Context (both text and JSON output)

Test plan

• ManagedFailureHandledTimestampTest — verifies timestamp is set when using deadLetterChannel, and lastExchangeFailureTimestamp remains null
• Existing ManagedRouteDumpStatsAsXmlTest and ManagedRouteDumpStatsAsJSonTest pass
• CI green

🤖 Generated with Claude Code

[gnodet]

Adds getLastExchangeFailureHandledTimestamp() to the management API MBean interfaces and dev consoles. Useful for operators monitoring when the last failure was handled — complements the existing failure counters with temporal information.

Implementation is consistent across MBean interfaces and dev console output.

LGTM.

Fully automatic review from Claude Code

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

• core/camel-console
• core/camel-management-api
• core/camel-management

ℹ️ Dependent modules were not tested because the total number of affected modules exceeded the threshold (50). Use the test-dependents label to force testing all dependents.

Build reactor — dependencies compiled but only changed modules were tested (3 modules)

• Camel :: Console
• Camel :: Management
• Camel :: Management API

---

⚙️ View full build and test results