Add test restarting compute at WAL page boundary

[arssher]

Problem

We've had similar test in test_logical_replication, but then removed it because it wasn't needed to trigger LR related bug. Restarting at WAL page boundary is still a useful test, so add it separately back.

Summary of changes

Add the test.

[github-actions]

7830 tests run: 7499 passed, 0 failed, 331 skipped (full report)

---

Flaky tests (12)

Postgres 17

• test_idle_checkpoints: debug-x86-64, debug-x86-64
• test_pageserver_small_inmemory_layers[False]: debug-x86-64
• test_scrubber_physical_gc_ancestors[None]: release-arm64, debug-x86-64
• test_timeline_archive[4]: debug-x86-64

Postgres 16

• test_physical_replication_config_mismatch_too_many_known_xids: release-arm64
• test_physical_replication_config_mismatch_max_locks_per_transaction: release-arm64

Postgres 15

• test_pgdata_import_smoke[8-1024-RelBlockSize.MULTIPLE_RELATION_SEGMENTS]: release-arm64
• test_pgdata_import_smoke[None-1024-RelBlockSize.MULTIPLE_RELATION_SEGMENTS]: release-arm64

Postgres 14

• test_pgdata_import_smoke[8-1024-RelBlockSize.MULTIPLE_RELATION_SEGMENTS]: release-arm64
• test_pgdata_import_smoke[None-1024-RelBlockSize.MULTIPLE_RELATION_SEGMENTS]: release-arm64

Code coverage* (full report)

• functions: 31.3% (8382 of 26760 functions)
• lines: 47.7% (65945 of 138291 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
4bce31d at 2024-12-12T16:48:14.082Z :recycle:}