bug: isQuotaLow() Checks Stale Quota Without Verifying resetTime

[karizcloud]

Description

quota-monitor.ts treats a token as still rate-limited even after its recorded resetTime has elapsed.

Steps to Reproduce

• Exhaust a GitHub token until its rate limit is reached.
• Wait until the recorded resetTime passes.
• Request a refresh.
• Observe that the request is still blocked because the stale quota state has not been re-evaluated.

Expected Behavior

• isQuotaLow() should only mark a token as low-quota when the current time is before its recorded resetTime.
• Once resetTime has passed, the token should be considered available again.
• The system should refresh or re-check the quota state instead of permanently blocking a token based on stale data.
• Users should be able to retry refresh requests once GitHub rate limits have reset.
• No token should remain blocked indefinitely due to stale cached quota values.

Screenshots / Logs

No response

GitHub Username (If applicable)

No response

Environment

Chrome