[Work_Item] Add data recency to metadata

[rileyjenk]

Problem Statement

Practitioners want to be able to understand how up to date FOCUS data is.

Objective

Capabilities:

• User does not have to inspect the FOCUS dataset to know how up to date the data is.
• Does not require an SLA
• Does not require a exact declaration of data accuracy
• Provider is able to specify how up to date the data is, and via documentation specify what their recency metadata indicates.
• Identify sector of times and when those times are invoiced

Supporting Documentation

Depending on the provider, the FOCUS data may be updated, replaced, modified or added to. Each providers mechanism for declaring this is different.

Link to AWS docs: https://docs.aws.amazon.com/cur/latest/userguide/understanding-report-versions.html

Proposed Solution / Approach

There was previous work done on this front in the v.5 days. I would like to pull that forward and rev on it as a proposed solution.

Epic or Theme Association

Provide the rational for the Epic or Theme.

Stakeholders

Provide names and roles of key stakeholders.

[shawnalpay]

@rileyjenk Thank you for standing up this work item, Riley! Could you add at least one use case in the format of our use-case library? Also, data examples will be very helpful in telling this story -- do any existing CSP exports support anything resembling the concept you propose, or is this an entirely net-new concept?

[jpradocueva]

Notes from Maintainers' call on November 4:

Context: Practitioners need visibility into data freshness, especially in environments where billing data is updated frequently. Adding metadata for data recency will allow practitioners to understand how current the data is. Level of Effort Required: Medium — Adding metadata fields is relatively straightforward, though ensuring accurate and timely data updates across providers may be challenging.