feat(report-module): implement Report_Module — widget, reports page, freeze cron

[MathieuLamiot]

Description

Moves Dashboard_Widget and Reports_Page registration and the `sybgo_freeze_weekly_report` cron callback from `Sybgo` into `Report_Module::boot()` and a new public named method `freeze_report_callback()`, making the freeze logic independently testable.

Closes #96

Type of change

• Sub-task of Introduce Feature Modules to own WP integration by domain #93
• Enhancement (non-breaking change which improves an existing functionality).

Detailed scenario

What was tested

1. Activated the plugin on a local wp-env install — no fatal errors; dashboard widget and reports page loaded correctly.
2. Navigated to WP Admin → Dashboard — widget displayed current-week event counts.
3. Navigated to WP Admin → Reports — reports list rendered with the active report row.
4. Ran wp cron event run sybgo_freeze_weekly_report — report froze successfully; confirmed in DB with wp db query "SELECT status FROM wp_sybgo_reports ORDER BY id DESC LIMIT 1" (showed frozen).

How to test

1. Check out feat/report-module-96 and run composer dump-autoload in wp-plugin/.
2. Boot wp-env: cd tests/e2e && npx wp-env start.
3. Run unit tests: cd wp-plugin && vendor/bin/phpunit --testsuite=Unit — 5 new ReportModuleTest tests pass.
4. Activate the plugin and navigate to WP Admin → Dashboard — widget should display.
5. Navigate to WP Admin → Reports — reports page should render.
6. Run wp cron event run sybgo_freeze_weekly_report — confirm the report is frozen in the DB.

Affected Features & Quality Assurance Scope

Dashboard widget, reports page, and the weekly freeze cron are the affected features — behaviour is identical, only wiring location changed. All other plugin features unchanged.

Technical description

Report_Module::boot() calls Admin_Manager::register_page() for both Dashboard_Widget and Reports_Page (built via private factory helpers that mirror the removed create_* methods from Sybgo). It calls Cron_Manager::register('sybgo_freeze_weekly_report', 'weekly', [$this, 'freeze_report_callback'], 'next Sunday 23:55').

freeze_report_callback() is public and named, which allows CronManager to store [$module, 'freeze_report_callback'] as a callable — this is what makes it unit-testable in isolation from boot().

Removed from class-sybgo.php: create_dashboard_widget(), create_reports_page(), freeze_weekly_report_callback(), and the dashboard widget / reports page lines inside init_admin(). The freeze scheduling and callback registration inside init_cron_schedules() are also removed.

New dependencies

None.

Risks

None identified. Dashboard widget, reports page, and freeze cron behaviour are unchanged; only the class that wires them differs.

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionable.

Unticked items justification

None.

Additional Checks

• In the case of complex code, I wrote comments to explain it.
• When possible, I prepared ways to observe the implemented system (logs, data, etc.)
• I added error handling logic when using functions that could throw errors (HTTP/API request, filesystem, etc.)