libsql-sqlite3: End read transaction in sqlite3PagerWalEndCommit()

We have a problem with WAL API where in some scenarios, we seem to lose
WAL frames that were already applied. However, inspecting the external
WAL frame, the sync mechanics work fine and the problem is in SQLite's
in-memory state.

As it turnws out, the sqlite3PagerWalBeginCommit() function first begins
a read transaction and then upgrades it to a write transaction. However,
sqlite3PagerWalEndCommit() only ends the write transaction and therefore
leaves the pager in READER state. Let's call pager_unlock() to switch to
OPEN stte, fixing the issue of disappearing frames.

Author: penberg

libsql-sqlite3/src/pager.c

@@ -7813,10 +7813,16 @@ int sqlite3PagerWalBeginCommit(Pager *pPager) {
 }
 
 int sqlite3PagerWalEndCommit(Pager *pPager) {
+  int rc = SQLITE_ERROR;
   if (!pagerUseWal(pPager)) {
-    return SQLITE_ERROR;
+    return rc;
+  }
+  rc = pPager->wal->methods.xEndWriteTransaction(pPager->wal->pData);
+  if (rc != SQLITE_OK) {
+    return rc;
   }
-  return pPager->wal->methods.xEndWriteTransaction(pPager->wal->pData);
+  pager_unlock(pPager);
+  return rc;
 }
 
 int sqlite3PagerWalInsert(Pager *pPager, unsigned int iFrame, void *pBuf, unsigned int nBuf) {