Migrate Azure Consumption to Cost Details API

[4upz]

Context

Overview

we need to transition from using the deprecated "Usage Details List" API for querying usage data to the new "Cost Details" API provided by the Azure's Cost Management service. This transition will involve updating the Azure package and making use of the "Cost Details" API for generating reports and fetching usage data.

Out of Scope:

• Storing historical rows in the cache or copying reports to the user's account using Azure blobs
• Implementing support for usage date via Exports
• Handling report expiration for date ranges

Related issues/Dependencies:

• SPIKE: Azure Cost Details API Migration #1204

Acceptance Criteria

• Replace all calls to the deprecated "Usage Details List" API with calls to the "Cost Details" API.
• Ensure that the code is updated to use the " @azure/arm-csotmanagement" library in place of the "@azure/arm-consumption" library.
• Implement logic to chunk API calls into manageable date ranges, and provide a configuration option to customize the maximum chunk size.
• Ensure that the code can handle a maximum time range of one month per report and is capable of handling historical data for up to 13 months prior.

Tech Tasks

• Update the test suite to cover the new API calls and edge cases.
• Execute Changesets to track code changes related to API replacement.
• Bump any packages that have been updated during the transition.
• If changes affect the client, API, or CLI packages, update the create-app templates accordingly.
• Run the test-create-app script to validate that the create-app templates still function correctly.

Tech Notes

• Create an ADR and Document the specific changes made to transition to the "Cost Details" API and any considerations or limitations encountered during this process. (See notes in spike ticket)
• Important: This should be considered a major update for the Azure package.

Review Tasks

• Conduct thorough testing to ensure that the transition does not introduce new bugs.
• Update the project documentation to reflect the new methodology for fetching subscription usage data -- including new instructions on connecting data via billing id or subscription id.