Rename duo_self_hosted AddOn to self_hosted_dap

Roy Zwambagrequested to merge
583583-rename-duo-self-hosted-addon-name into master

What does this MR do and why?

Renames the duo_self_hosted AddOn to duo_self_hosted_dap to eliminate confusion with Self-Hosted Models for Duo Enterprise, which is a different offering. The new name clarifies that this AddOn is specifically for the Self-Hosted Duo Agent Platform (DAP).

Changes

  • Renamed the AddOn constant from DUO_SELF_HOSTED to DUO_SELF_HOSTED_DAP in constants and models
  • Updated all references in service classes, scopes, and factory traits
  • Updated user-facing strings to "GitLab Self-Hosted Duo Agent Platform"
  • Created database migration to rename existing duo_self_hosted entries to duo_self_hosted_dap in subscription_user_add_on_assignment_versions
  • Updated all tests to use the new naming convention

Migration

Since we do not provision this AddOn yet, we might not need this migration

[ gprd ] production> GitlabSubscriptions::UserAddOnAssignmentVersion.distinct.pluck(:add_on_name)
=> ["code_suggestions", "duo_core", "duo_enterprise"]

What would happen if we provision this pre-18.7 - CustomersDot will send over provision params with the new name duo_self_hosted_dap, and then we can not store it?

Related to

Closes #583583

Edited by Roy Zwambag

Merge request reports