Followup fix OAuth token Database Load Balancer logic in more generic location

The following discussion from !211007 (merged) should be addressed:

• @mkaeppler started a discussion: (+1 comment)

  question: The way the problem is described sounds like it would affect all OAuth tokens, but this solution is specific to Duo Workflow. What is different about how Duo Workflow issues OAuth tokens that triggers this problem? This was not clear to me from the MR/problem description 🤔