Update SecretsCheck to use the Secret Detection Service for .com and dedicated with 1-way communication

Purpose

The Secret Detection Service(SDS) will be used by Gitlab.com and dedicated customers. Self-managed customers will continue to use the current logic included in the gem.

This first issue is intended to implement a minimum, viable change to support 1-way communication with the SDS to start gathering metrics for a full rollout.

Implementation plan

  1. Copy client class from SDS to monolith codebase
  2. Add migrations to add secret detection URL and auth token to ApplicationSettings
  3. Maybe use Gitlab Secrets Manager instead? I don’t think it’s ready…?
  4. Add minimal UI to set URL and auth token (?)
  5. Look into how Duo handles this
  6. Modify SecretsCheck to call the SDS and ignore response
Edited by Ethan Urie