Y26-126 - As a manager in Short Read in charge of billing I want `custom_primer_used`, `kit_type`, `cycle_number`, `qc_complete_date` columns available in `billing_report_view_v2`

[dn10-sanger]

User story

As a manager in short read in charge of billing I want custom_primer_used, kit_type, cycle_number, qc_complete_date columns available in billing_report_view_v2 so that the view has all fields for cross-charging and date range validation.

Context
The new billing_report_view_v2 is missing four fields that are present in the original query and required for cross-charging: NovaSeq X specific - custom_primer_used, kit_type, cycle_number and qc_complete_date useful for verifying the correct date range has been selected at cross-charging.

Who are the primary contacts for this story
Tom W
Ivy T
Laura H
Rich R
Dikshita N

Who is the nominated tester for UAT
We can test this ourselves.

Acceptance criteria

To be considered successful the solution must allow:

• custom_primer_used, kit_type, cycle_number and qc_complete_date are present in billing_report_view_v2
• All four columns are present in the final SELECT of billing_report_view_v2
• Values for all four columns match those returned by billing_report_view for the same runs.
• A side-by-side comparison of billing_report_view_v2 and billing_report_view confirms all expected columns are present and no columns have been unintentionally dropped.
• Updated view is deployed and confirmed with Matt.

References
This story has a non-blocking relationship with:
sanger/ sample-tracking #51