Fix GitLab Performance Monitoring content types for Doorkeeper
What does this MR do?
This MR ensures GitLab Performance Monitoring doesn't rely on a Devise specific method that isn't always available.
Does this MR meet the acceptance criteria?
-
Tests added for this feature/bug - Conform by the code review guidelines
-
Has been reviewed by a Backend maintainer -
Has been reviewed by a Database specialist
-
-
Conform by the merge request performance guides -
Conform by the style guides -
End-to-end tests pass ( package-and-qamanual pipeline job)
What are the relevant issue numbers?
Edited by Nick Thomas