Enhancement: Re-implement optimized caching for Verification Request board

## Background Information
After introducing the ability to approve or decline Verification Requests directly from the newly added modal on the page — based on parameters defined by the AI Task process — the page is no longer a read-only view.
Because the status and other metadata can now change as a result of moderation updates, we removed caching to ensure users always see the most recent state of the request.

However, completely disabling cache introduces performance drawbacks and increases server load.
A better, more optimized caching strategy should be implemented.

---

## Steps to Reproduce
1. Open a Verification Request page in a browser
2. Approve or decline the corresponding request from the board
3. Reopen the Verification Request page
4. Observe that the page fully reloads from the server with no caching applied

---

## How
Reintroduce smart caching by:
- Allowing short-term caching when content is unlikely to change
- Using conditional requests or `must-revalidate`
- Invalidating only when status or topics are updated

---

## Expected Behavior
- Faster page loading thanks to effective caching
- Content updates quickly after moderation changes (no stale data)
- Reduced backend workload and improved scalability