setbacklog will fail if retention policies cache not updated immediately

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. set retention policies which routed to broker 1
2. set backlog policies which routed to broker 2
3. broker 2 checkBacklogQuota which will fail sometimes


because the retention cache in broker 2 was updated immediately

**Expected behavior**
A clear and concise description of what you expected to happen.

invalidate the retention cache first

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: [e.g. iOS]

**Additional context**
Add any other context about the problem here.

Reproduce the issue using the listed retention-policy and backlog-policy routing steps, then inspect the broker handling for retention and backlog quota checks. The fix is complete when the retention cache is invalidated before the backlog policy is checked, preventing the intermittent failure on broker 2.

Written by the indexing model from the issue text.