Summary

This epic expands the option to view AWS cost by cost type to the Amazon Web Services filtered by OpenShift views in the UI.
For API users this adds the cost_type param to the api/cost-management/v1/reports/openshift/infrastructures/aws/costs/ API endpoint with options unblended_cost, blended_cost, and savingsplan_effective_cost.

Finally, "raw" costs in our OpenShift views (api/cost-management/v1/reports/openshift/costs for API users) will now default to using the savings plan effective cost over the unblended cost when the OpenShift node and corresponding EC2 instance are part of a compute savings plan in AWS. Previously, we used the unblended cost regardless. The end result should be a total OpenShift cost that does not appear artificially high for customers using savings plans.

Details

We need to enable savingsplan_effective_cost and blended_cost for OCP on AWS