fix(samples): [Cache Tracing 22] Fix cache evict system test to match actual span op

[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
• #5190 — Port cache tracing to Spring Boot 3 Jakarta + samples
• #5191 — Port cache tracing to Spring Boot 2 + samples
• #5192 — Skip cache span data when child span is NoOp
• #5201 — Add db.operation.name attribute to cache spans
• #5202 — Instrument putIfAbsent, replace, and getAndReplace
• #5203 — Fix cache hit detection for typed get and fix jcache docs link
• #5204 — Use method-specific span operations for cache spans
• #5205 — Merge startSpan helpers into shared core method
• #5206 — Move operation attribute to centralized CACHE_OPERATION_KEY constant
• #5207 — Add cache.write boolean span attribute
• #5208 — Use comma-joined keys as span description for bulk JCache operations
• #5209 — Remove _KEY suffix from cache SpanDataConvention constants
• #5210 — Fix get(key, type) double-call in SentryCacheWrapper
• This PR — Fix cache evict system test to match actual span op

---

📜 Description

Updates CacheSystemTest.cache evict produces span across all 9 Spring Boot sample modules to check for cache.evict instead of cache.remove. The test was written expecting the spec op name, but the implementation uses the Spring method name as the span operation.

💡 Motivation and Context

The cache evict produces span system test was failing across the entire Spring Boot CI matrix because it asserted cache.remove while the code emits cache.evict. This is a test/code alignment fix — the non-standard op names are a known issue tracked separately.

💚 How did you test it?

Test-only change. Updated the assertion in all 9 copies of CacheSystemTest.kt.

📝 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

⚠️ 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

🟢 Patch (bug fixes)

📋 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.}

[sentry]

Sentry Build Distribution

App Name	App ID	Version	Configuration	Install Page
SDK Size	io.sentry.tests.size	8.34.1 (1)	release	Install Build