feat(spring7): [Cache Tracing 8] Add retrieve() overrides for reactive/async cache support

[adinauer]

PR Stack (Cache Tracing)

• #5172 — Add SentryCacheWrapper and SentryCacheManagerWrapper
• #5173 — Add enableCacheTracing option
• #5174 — Add BeanPostProcessor and auto-configuration
• #5175 — Add cache tracing e2e sample
• #5179 — Add SentryJCacheWrapper for JCache (JSR-107)
• #5182 — Add JCache console sample
• #5183 — Add cache tracing to all Spring Boot 4 samples
• #5184 — Add retrieve() overrides for reactive/async cache support

---

📜 Description

Adds retrieve(Object key) and retrieve(Object key, Supplier<CompletableFuture<T>>) overrides to SentryCacheWrapper.

Spring 6.1+ added these two methods to the Cache interface for non-blocking cache operations. Spring's CacheInterceptor calls them when @Cacheable is placed on methods returning CompletableFuture<T> or Mono<T>. Without these overrides, the default Cache.retrieve() throws UnsupportedOperationException, meaning any app using reactive @Cacheable with cache tracing enabled would crash.

Key design decisions:

• Spans are started synchronously and finished asynchronously via CompletableFuture.whenComplete()
• retrieve(key) handles three result states: null return (immediate miss), CF resolving to null (late miss), CF resolving to value (hit)
• retrieve(key, valueLoader) uses the same AtomicBoolean loader-tracking pattern as get(key, Callable) for cache hit detection

💡 Motivation and Context

This is a functional bug fix. The SentryCacheWrapper implements Cache but didn't override the retrieve() default methods, which throw UnsupportedOperationException. When cache tracing is enabled and the wrapper intercepts the cache, reactive @Cacheable methods crash instead of working.

💚 How did you test it?

• 10 new unit tests in SentryCacheWrapperTest covering:
  • Cache hit/miss detection for both retrieve variants
  • Immediate null return vs late-determined null
  • Async error handling (failed futures)
  • Synchronous delegate exceptions
  • No-span behavior when tracing disabled

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

Port retrieve() overrides to sentry-spring-jakarta when cache classes are ported there.

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.

#skip-changelog

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

This PR will not appear in the changelog.

---

_{🤖 This preview updates automatically when you update the PR.}

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 41872ad

[adinauer]

cursor review

[adinauer]

@sentry review

[sentry]

Sentry Build Distribution

App	Version	Configuration
SDK Size	8.34.1 (1)	release

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	366.36 ms	466.94 ms	100.58 ms
Size	0 B	0 B	0 B

Baseline results on branch: feat/cache-tracing-all-samples

Startup times

Revision	Plain	With Sentry	Diff
9ce8a42	333.64 ms	422.30 ms	88.66 ms

App size

Revision	Plain	With Sentry	Diff
9ce8a42	0 B	0 B	0 B