Update SeatLinkData to Use HistoricalData for Add-on Metrics
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Background
We currently track add-on metrics as part of seat link records for online cloud licenses to provide visibility into Duo seat adoption for Self-Managed customers.
Now that offline cloud license customers can purchase Duo Enterprise, we will need to capture this same adoption data from these users and ensure these metrics are part of the offline license data sharing process.
In order to allow the offline cloud license usage export file to contain these add-on metrics, we will need to start tracking this as part of GitLab's historical license data.
Proposal
Currently, the SeatLinkData calculates add_on_metrics at runtime during the time of the license seat link sync process. Other information transferred as part of seat links, like the timestamp, default_billable_users_count and default_max_count, are all taken from the license historical data instead, which is generated daily as part of the HistoricalDataWorker.
Once we start tracking the add_on_metrics as part of the historical data in Track add_on_metrics in HistoricalData (#551173), we should update the SeatLinkData to also use the stored add_on_metrics from the historical data for consistency.