CCC-2211: Add CUR 2.0 Template for CCM CloudFormation Setup Method

[t-omalley]

Note: Please remember to review the contribution guidelines
if you have not yet done so.

What does this PR do?

• Adds a CloudFormation template to set up CUR 2.0 configs in CCM
• Updates documentation in the relevant README

Testing Guidelines

• Tested E2E CloudFormation setup flow by uploading the new template into team's test bucket

[t-omalley]

• CCC-2211: Add CUR 2.0 Template for CCM CloudFormation Setup Method #334 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[hinosxz]

issue (correctness): Include the split cost allocation columns in the CUR 2.0 query

The table configuration enables INCLUDE_SPLIT_COST_ALLOCATION_DATA, but the SELECT list stops at tags and omits the split_line_item_* columns. The merged aws_cloud_cost_cur2 template selects these fields; without them, the exported Parquet files will not contain the split cost allocation data Datadog expects even though the export advertises it.

— Codex

[hinosxz]

that's a good catch, it's not in the minimal set of columns we require so we probably want to not include the split cost allocation by default. It'd be exporting more data than we need

[t-omalley]

Ok, just changed it to INCLUDE_SPLIT_COST_ALLOCATION_DATA: "FALSE"

[hinosxz]

might be out of my depth here so i'll let aws ints confirm but 2 main.yaml files feels like a weird pattern. should we just update the template that David created previously?

[t-omalley]

Yeah I can see why it's not ideal. If we updated David's template then the two CUR versions would have a different release.sh, and our existing one is already integrated into this repo's CI (so it doesn't need to be manually run).

[dhan0779]

I'm honestly OK with having just one template here (updating mine or just using yours). Feel free to remove mine in this PR, since long term we'll probably be only using just one of these anyways.