fix(deps): update dependency com.github.ben-manes.caffeine:caffeine to v2.9.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
com.github.ben-manes.caffeine:caffeine	2.9.2 → 2.9.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

ben-manes/caffeine (com.github.ben-manes.caffeine:caffeine)

v2.9.3: 2.9.3

Compare Source

Cache

• Fixed reference eviction when used with a broken executor (JDK-8274349)
• Reduced the entry overhead by 8 bytes when using weak or soft values
• Suppressed log warnings if a future is cancelled or times out (#​597)
• Fixed Map.entrySet.contains(o) to use reference equality
• Fixed early expiration of in-flight async loads (#​625)

JCache

• close() will now shutdown the executor and wait for in-flight loads to finish

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

• This PR fixes #123 or Fixes: #123

• This PR closes #123 or Closes: #123

• This PR resolves #123 or Resolves: #123

• Other supported keywords: fix, fixed, close, closed, resolve, resolved
  Option 2: Link via GitHub UI (Note: won't clear the failed check)

1. Go to the PR → Development section (right sidebar)

2. Click "Link issue" and select an existing issue

3. Push a new commit or re-run the workflow to clear the failed check
   Option 3: Use branch naming
   Create a new branch with one of these patterns:

• 123-feature-description (number at start)

• issue-123-feature-description (issue-number at start)

• feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow