refactor: update exception handling to use specific exception types

[zeitlinger]

No description provided.

[Copilot]

Pull request overview

This PR refactors exception handling throughout the codebase to use more specific exception types instead of catching generic Exception, improving code clarity and making the expected failure modes more explicit.

Changes:

• Narrowed catch blocks from Exception to specific exception types (RuntimeException, IOException, UnsupportedOperationException, ReflectiveOperationException)
• Added explicit null check for InputStream in PrometheusInstrumentationScope before use
• Updated exception handling comments to be more descriptive
• Removed .havingRootCause() assertions in tests to match the simplified exception wrapping behavior

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
JvmNativeMemoryMetrics.java	Changed catch block from Exception to RuntimeException and improved comment to clarify what runtime failures are caught
AbstractDropwizardExports.java	Changed catch block from Exception to RuntimeException for metric collection errors
CacheMetricsCollector.java	Changed catch block from Exception to UnsupportedOperationException to specifically handle unavailable evictionWeight metric
PrometheusInstrumentationScopeTest.java	Removed .havingRootCause() assertions as IllegalStateExceptions now propagate directly without wrapping
PrometheusInstrumentationScope.java	Changed catch block to IOException only, added explicit null check for InputStream, and added required imports
OtelAutoConfig.java	Changed catch block from Exception to ReflectiveOperationException for reflection operations
HttpExchangeAdapter.java	Changed catch block from Exception to IOException for error response writing

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.