As an API consumer, I'd like to be able to query all PAYG products (and not just SaaS contracts) with the billing category parameter. This will allow the same GUI updates for SaaS contracts to be used for all SaaS products.

The expectation from a customer point of view is that billing_category=on-demand should show all previous usage for any PAYG product, and because in SWATCH-1165, we are updating data going forward to produce DAILY rollups, we need to also retroactively create records for existing PAYG product data.

Note, we can use https://github.com/RedHatInsights/rhsm-subscriptions/blob/5244852539f7739140449cb1dceeee3a6c9b5703/src/main/java/org/candlepin/subscriptions/tally/billing/RemittanceController.java#L69  as a starting point.

We need to expand the scope of data that remittance controller operates on to all existing hourly snapshot data.

Additionally, the remittance recalculation should fetch the existing record to use as a baseline and fail without making any data changes if the recalculated total doesn't match the existing record total. The existing record(s) should be replaced if the total matches.

DONE:

• All existing PAYG remittance (which will be marked as HOURLY) has corresponding aggregations in the form of DAILY rollups.
• This should be triggered off of an internal API after deployment.
  • See syncRemittance and its invocation from InternalTallyResource
• If the API is hit multiple times, it should attempt to reconcile again.
• Remittance controller updated to recalculate remittance records for all hourly snapshots and replace (if the existing remittance total matches), or warn and fail (if the existing remittance total does not match).