Simply uncomment the billingFactor for OSD cores to 0.25 in tag_profile.yaml - in a separate release (to be done only after the prior work lands).

In order to support updating billing factors, when fetching recorded billable usage, derive the implied raw value by multiplying the inverse of the recorded billing factor (e.g. 1.0 / 0.25) by the remitted value. Then convert this to the configured billingFactor by multiplying by the currently configured billingFactor. The usage record should be updated with the configured billingFactor. This is where the added complexity is and definitely needs extensive testing. This logic should be applied in BillableUsageController.calculateBillableUsage use TagMetric to use the configured billingFactor field from the tag_profile.yaml to make sure that osd's new value is update correctly.