[datlechin]

Summary

• SQLite and libSQL restores get their own confirmation: sqlite3 -bail stops at the first error, and a backup TablePro wrote is one transaction, so none of it is kept. A dump that is not one transaction keeps what ran before the error. The sheet used to say existing objects are kept and the dump's data added.
• MySQL and MariaDB: the confirmation says the restore stops at the first error (mysql runs without --force) and keeps what ran before it, and that a TablePro backup overwrites each object it names.
• PostgreSQL, Redshift and MongoDB: the confirmation adds that the restore carries on past errors.
• apple/scripts/probes/check-restore-error-semantics.sh checks these facts against sqlite3, the mysql family and pg_restore.
• RestoreConfirmationTextTests.appendingEnginesKeepExistingObjects pinned SQLite to the old text; it now covers PostgreSQL, Redshift and MongoDB only, and SQLite and MySQL get their own cases.

Docs: TableProApp/docs#162

Test plan

• RestoreConfirmationTextTests: sqliteStopsAtTheFirstError and mySQLStopsAtTheFirstError fail on main.
• Probe run against sqlite3 3.54.0 and 3.54.1, MariaDB 13.0.2 (client and server) and pg_restore 17.11: all facts hold. With -bail removed, the SQLite checks fail.