PM-5719: Include projected member payments

[jmgasper]

What was broken

The Member Payment $ by Month and Member Payment $ by Customer dashboards omitted owed and on-hold payments. In QA's July example, both charts showed only an incorrect $51 contest value while Wallet Admin also contained TAAS, task, and engagement payments.

Root cause

The two PM-5719 queries selected only PAID records and grouped them by date_paid. The established Reports dashboard and Wallet Admin semantics use current non-cancelled payments in their creation month so projected amounts remain visible.

What was changed

• Updated both member-payment queries to select latest non-cancelled payment records and group them by created_at.
• Preserved the existing gross-amount calculation, payment categorization, billing-account customer resolution, top-five ranking, and Other Customers grouping.
• Updated the dashboard documentation to describe the corrected projection semantics.

Live finance-source validation for July now resolves to TAAS $3, Task $68, Contest $1,635, and Engagement $3,780, totaling $5,486. The source's distinct member counts also match the established Members Paid dashboard in every category.

Any added/updated tests

• Updated SQL regression coverage for both payment dashboards to require non-cancelled records grouped by creation month and reject PAID/date_paid filtering.
• All 5 dashboard suites and 35 tests pass.
• The production build and changed-file ESLint check pass.
• The full suite was run: 19 suites and 338 tests pass. The same 3 unrelated SFDC/report-directory suites already documented on the previous attempt still fail on unchanged paths.
• The repository lint script completes after auto-fixing 3 pre-existing leaderboard formatting issues on develop; those unrelated auto-fixes were intentionally excluded from this scoped PR.