Default deduplication drops distinct Netty read timeout occurrences #6365

Hi,

Netty's ReadTimeoutHandler reuses ReadTimeoutException.INSTANCE across separate timeout occurrences.

With enableDeduplication=true (the default), Sentry stores the throwable in a WeakHashMap and drops subsequent events containing the same instance. Since Netty holds a static reference to it, the entry remains reachable, potentially suppressing timeouts from unrelated requests.

Setting enableDeduplication=false avoids this but disables deduplication globally. The same logic remains in Sentry Java 8.61.1.

Our environment

• Sentry core / sentry-logback: 6.23.0
• sentry-spring-boot-starter-jakarta / sentry-spring-jakarta: 6.14.0
• Netty: 4.1.117.Final
• Reactor Netty: 1.2.2

Would you consider this a bug? If so, would you be open to a PR addressing it?