fix: strict change detection in TableTestState

[AZabolotnikov]

refs: #290

[Copilot]

Pull request overview

This PR fixes the TableTestState::getChanges() method which previously used array_diff_assoc() for change detection. That function performs loose comparison after string casting, so transitions like null → false, null → 0, or null → "" were not detected as changes. The fix replaces it with array_filter using strict (!==) comparison, and adds a test plus fixtures to cover the regression.

Changes:

• Replace array_diff_assoc with strict per-key comparison in getChanges().
• Add testAssertChangesCompareStrict to validate detection of null ↔ falsy transitions.
• Add input/expected fixtures for the new test case.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/Testing/TableTestState.php	Use array_filter with !== for strict change detection.
tests/TableTestStateTest.php	New test case covering strict comparison behavior.
tests/fixtures/TableTestStateTest/compare_not_strict_fields/initial_dataset.json	Initial dataset with null fields.
tests/fixtures/TableTestStateTest/compare_not_strict_fields/changed_dataset.json	Updated dataset with falsy non-null fields.
tests/fixtures/TableTestStateTest/db_changes/test_models/assertion_compare_strict_fields.json	Expected diff output.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.