Check if addon is purchased for user, not seat assigments
What does this MR do and why?
When self-issuging a token (for Gitlab.com) check if add-on is purchased for a user, instead of checking if user is assigned to a seat assignments.
Duo Nano will not have seat assigments and we are issuing an instance token here, so we only want to issue a token based on purchase record, not seat assigments. This also reduces the gap between SelfManaged customers and Gitlab.com.
References
Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/526570
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.