The project monthly rate distribution is a little bit more complicated than cluster, node, or pcv distribution. The challenging element to the project distribution is that we need to account for the monthly rate being a monthly cost, while the project cost is hourly. In order to do this we will need to implement a rolling window. 

Therefore the way we configure the project’s cost is:

• (pod usage for entire project's month to date) / (pod usage for entire cluster's month to date) x cluster cost

Since the project cost will have to be deleted and updated regularly, it is probably better to separate it into its own fields in the daily summary tables.

• infrastructure_project_monthly_cost
• supplementary_project_monthly_cost

We should follow a similar json structure that we created in the previous issue for the monthly project cost.