Generic/special tag matching for OCP on AWS with multiple clusters pointing to the same AWS source does not match consistently. The same generic tag across multiple clusters only seems to apply to one cluster when in theory it should match both. It should be determined why this data is only matching one cluster and if we can improve OCP on Cloud tag matching to match specific tags over generic tags to minimize the risk of a generic tag matching the wrong cluster when it should be identified via special tags.

It turns out we are applying the cost from the generic `cluster` tag to all namespaces even if it did not apply incorrectly distributing costs. Since this `cluster` tag was undocumented and only being used by internal teams, we removed the special cluster tag matching.

Relevant slack conversation: https://redhat-internal.slack.com/archives/C04476G1F7H/p1711548048381909