During the live restore project we added logic to WiredTiger to catch a potential avenue of database corruption. The logic prevents WiredTiger from starting up, without live restore options, when opened on a database that appears to have an in progress live restore. The relevant function call is:

__wt_live_restore_validate_non_lr_system.

Effectively we should exercise this code path in a python test and demonstrate it throwing an EINVAL error.

The steps to do so would be:

1. Open a live restore on a database, and specify 0 background threads. This will create an in progress live restore that cannot finish.
2. Close the database connection
3. Reopen it without any live restore configuration and we should see the error.