Calculate TotalThroughput as the maximum organization-wide daily total

[rebchr]

Fixes:

• TotalThroughput in the throughput report is the sum of per-endpoint peaks, not the peak daily total #5592

What

TotalThroughput in the throughput report is now the maximum over calendar days of the organization-wide daily total, instead of the sum of each endpoint's individual best day. This matches the published definition of maximum message throughput per day at particular.net/pricing/definitions:

The maximum number of messages processed by all NServiceBus endpoints across the entire organization in a day.

Why

The previous calculation (queueThroughputs.Sum(q => q.Throughput), where each queue's Throughput is its own peak day) counts every endpoint's peak as if they all occurred on the same day. Unless all endpoints peak simultaneously, this is strictly greater than the actual busiest day, and the overstatement grows with the number of queues and the length of the reporting window. Since the report is used in licensing conversations, the reported number should match the definition it is measured against.

Example — two endpoints, two days: A = [100, 10], B = [20, 100]. Previous TotalThroughput: 200. Actual busiest day: 120.

How

• New DailyThroughput() extension yields an endpoint's per-day values; when multiple sources have data for the same day, the maximum value is used, consistent with the existing per-endpoint MaxDailyThroughput() semantics (all sources measure the same messages).
• GenerateThroughputReport accumulates daily totals across all endpoints in the existing loop and sets TotalThroughput to the highest daily total (0 when there is no data).
• The per-queue Throughput field is unchanged, so TotalThroughput remains ≥ every per-queue value. The set of queues contributing to the total is also unchanged.
• Added a test that encodes the definition (endpoints peaking on different days). Updated the one assertion and one approval file that encoded the previous sum-of-peaks behavior (195 → 185, 249 → 238).

All tests in Particular.LicensingComponent.UnitTests pass (75/75).

🤖 Generated with Claude Code

[CLAassistant]

All committers have signed the CLA.

[PhilBastian]

Thanks @rebchr, we're reviewing your PR. The TotalThroughput value in this report is not used by Particular for determining Tier, which is likely why it's never been picked up before that the calculation was incorrect. We perform a calculation from the raw daily values that looks very similar to what you've done here 😄.
I'm thinking that this field should be removed entirely...

[rebchr]

Hi Phil, thanks for the quick response — good to hear the tier calculation is done from the raw daily values on your side, and that it aligns with what this PR does. Since the daily values for queues marked NotNServiceBusEndpoint are stripped from the report, we're assuming that calculation also only covers actual NServiceBus endpoints.

Removing the field entirely would work just as well for us. The reason we care is that the pre-computed total does end up in licensing conversations in practice: during our 2025 renewal the combined reports were quoted to us as "11+ million" throughput, while the actual busiest day computed from the daily values was ~8.4 million. Whichever way it's resolved — corrected or removed — the important thing is that the report no longer presents a total that contradicts the published definition.