Don't cache overdrive token in credentials table (PP-1717)

[jonathangreen]

Description

Don't cache the overdrive authentication token in the credentials table. Instead just refresh it when we need it. This prevents multiple threads / processes from getting into a deadlock waiting on postgres transactions that are all trying to update the same credential object.

Motivation and Context

Debugging the deadlock in PP-1717, and this is a factor in that deadlock. It may not be the only issue, but its one of the factors causing this deadlock.

This will mean calling out to get a session token slightly more often, but it shouldn't matter doing one extra call to their API now and then. If we were really concerned we could cache these in redis, but it doesn't seem worth the effort.

How Has This Been Tested?

• Tested locally

Checklist

• I have updated the documentation accordingly.
• All new and existing tests passed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.79%. Comparing base (96b10e6) to head (eb2ace5).
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2060   +/-   ##
=======================================
  Coverage   90.79%   90.79%           
=======================================
  Files         343      343           
  Lines       40584    40579    -5     
  Branches     8790     8788    -2     
=======================================
- Hits        36847    36843    -4     
  Misses       2483     2483           
+ Partials     1254     1253    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tdilauro]

Looks good! 🚀