Split attribution rate-limit into separate event & aggregate rate-limits

[vikassahu29]

Currently, we have a single rate-limit which counts the overall attribution (either event or aggregate or both) of the trigger. This change separates the attribution counts for event & aggregate for accurate counting of reported conversions. This will facilitate easier report deletions counting as well as accurate counting for Full Flex proposal where more than 1 event report may be generated per trigger.

Deletion Issue:

1. Let's say there is 1 source (event) which is registered at t = 0: S
2. Trigger T1 registered at T = 1 and generates an event report E1 (priority=1) and no aggregatable reports
3. Trigger T2 registered at T = 2 and generates an event report E2 (priority=2) and no aggregatable reports. E2 will replace E1 here due to higher priority.

Current Implementation:

We will count this as 2 attribution which is incorrect because E1 is never delivered.

With Proposed Changes:

We will count this as 1 event-attribution for E2 and 0 for E1 (rate-limit is deleted when we replace the report)

---

Preview | Diff