feature(node): Add instrumentation to the handler in Hono

[Karibash]

⚠️ This PR depends on #17366 and should be merged after it.

Summary

This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities, and thorough test coverage. The changes build upon the basic Hono integration to provide a complete tracing and error monitoring solution.

New Features

• Handler Instrumentation: Added instrumentation for Hono handlers and middleware, providing detailed tracing capabilities
• Error Handler: Implemented setupHonoErrorHandler() function to capture and report errors to Sentry with configurable error filtering
• Public API: Added Hono integration to the main package exports, making it available as @sentry/node
• Tracing Module: Included Hono integration in the tracing integrations index

Bug Fixes

• CJS Compatibility: Fixed an issue where applying patches failed in CommonJS environments
• Type Corrections: Fixed incorrect MiddlewareHandler type definition to ensure proper TypeScript support

Implementation Details

• Instrumentation: Created HonoInstrumentation class that wraps Hono middleware handlers via class extension instead of function replacement for better compatibility
• Type Definitions: Added comprehensive TypeScript type definitions vendored from Hono's official types
• Constants: Defined Hono-specific attribute names for OpenTelemetry integration
• CJS Compatibility: Fixed patching issues in CommonJS environments

Testing

• Integration Tests: Added comprehensive test suite covering:
  • ESM and CJS compatibility
  • Multiple HTTP methods (GET, POST, PUT, DELETE, PATCH)
  • Various route patterns (sync/async, different paths)
  • Middleware and handler instrumentation verification
  • Error handling scenarios
  • Span attribute validation

Related Issue

close #15260

[cursor]

Bug: Promise Handling Flaws in _safeExecute Method

The _safeExecute method has a few issues with promise handling. It incorrectly detects thenable objects by checking for then as an own property, which means spans for async handlers may end prematurely. Additionally, it returns the original promise while attaching new .then() handlers, which can lead to unhandled rejections or inconsistent error flow. The method's return type annotation is also incorrect.