Azure mapping of Usage Type and Usage Family change to align with other CSPs

Currently, Usage Type is a concatenation of the Meter Category and Meter SubCategory columns from the Azure Billing Export Report (or the cost data API endpoint). This prevents a one-to-one comparison of CLDY to the source data since a combining of two fields is occurring.

Usage Family does not match any of the fields in the Billing Export and appears to be sourced by ATUM data, which is not vendor data. Since ATUM data already exists as available dimensions, this is a unnecessary duplication of data.

By changing Usage Type and Usage Family for Azure data to source from Meter SubCategory and Meter Category respectively, we will more closely align with AWS and GCP's use of those fields.

An added benefit of the mapping I propose above is smaller datasets in reports. Currently, MeterCategory and MeterSubCategory being concatenated together increases the dataset of reports that are only looking one or the other columns. Say I only want to look at my storage costs (and I am unfamiliar with the ATUM columns), currently, I would filter Usage Type to Storage.X and have a much larger list due to the aggregation on that column.

This change would also reduce calculations at time of ingestion. A concatenation is a relative low effort calculation for most systems, but when done over hundreds of thousands of rows of data, it adds up. There is little reason to concatenate these fields when Usage Family is not properly mapped.