fix(trakt): improve invalid token handling and token check scheduling

[krbrs]

Summary

This PR improves Trakt OAuth failure handling and recurring token-check behavior when Trakt credentials are revoked, expired, or otherwise become invalid.

Previously, revoked or expired Trakt auth could still leave Shoko relying on the stored Unix expiry timestamp, continue scheduling the recurring token-check job even when Trakt was disabled, and produce noisy error logging during expected OAuth/device-auth failure paths.

Changes

Trakt refresh handling

• Detect invalid_grant responses during Trakt token refresh
• Treat revoked or expired refresh tokens as expected deauthorization
• Disable Trakt automatically when refresh tokens are revoked or expired
• Clear invalid auth state safely
• Prevent repeated refresh attempts with permanently invalid refresh tokens
• Reduce noisy logging for expected OAuth revoke flows

Token validity check

• Validate the current Trakt access token with a lightweight authenticated API call before trusting the stored expiry timestamp
• Refresh immediately if the current access token is no longer valid, even if the saved Unix expiry has not elapsed
• Fall back to the stored expiry timestamp only when token validity cannot be confirmed

Scheduling

• Only schedule the recurring CheckTraktTokenJob when Trakt is enabled
• Remove the persisted recurring Trakt token-check job when Trakt is disabled, so old Quartz state does not keep firing it

Cleanup

• Refactor SendData() stream handling to use using declarations for safer disposal
• Replace brittle raw OAuth error string matching with JSON parsing
• Use named Trakt status constants consistently for expected device-auth polling statuses

Result

Revoked or expired Trakt tokens now:

• fail gracefully
• disable Trakt until re-authenticated
• are detected even if the stored expiry timestamp has not elapsed
• avoid repeated retry/error loops
• avoid noisy expected OAuth/device-auth error logging

When Trakt is disabled:

• the recurring token-check job is no longer scheduled
• previously persisted recurring token-check jobs are removed

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud