Tests that need to simulate a page server having already reclaimed a layered table's stable pages currently hand-edit Palite's SQLite pages table directly (test/suite/helpers/helper_disagg.py delete_all_table_pages / _palite_mutate run sqlite3 against kv_home/pages_NN.db).

It would be cleaner and less brittle for Palite itself to expose this as a debug/test capability - e.g. a trim_table that actually deletes, or a dedicated discard/delete hook on the page-log handle — so tests drive the deletion through the page-log interface rather than poking Palite's storage.

Raised during review of WT-18101 (test_layered_drop02.py).