Reduce noise of exclusive lease lock for PersonalAccessTokens::LastUsedService

Summary

Same as #331033 (closed) MR to fix previous issue: !126914 (merged)

Customers, as well as GitLab.com, sees a very large amount of errors for the PersonalAccessTokens::LastUsedService, with the message Cannot obtain an exclusive lease. There must be another instance already in execution.

On GitLab.com, we see about 500k of these errors every hour.

For a specific customer's Webservice Kubernetes pod log, we saw about 99% of the logs were this specific error. This equated to about 2000-4500 log entries every minute.

Steps to reproduce

Unknown

Example Project

What is the current bug behavior?

Extremely verbose error message

What is the expected correct behavior?

This lease log entries is not produced.

Relevant logs and/or screenshots

https://log.gprd.gitlab.net/app/r/s/4bwut

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.