test: the popup boot's stand-in for filterTransactions returns the real shape (closes #429)

The stand-in in tests/support/popupBoot.js returned a bare list, while the
real filterTransactions returns { transactions, newFraudContracts }. Home,
AddressDetail and AddressToken read both fields, so every test boot onto
one of them threw inside its transaction loading, logged loadHomeTxs failed
or loadTransactions failed, and never ran the rest of that code. The
stand-in now returns the real shape, and tests/persistedFieldContract.test.js
boots onto each of the three views and asserts neither message is logged.

Model: opus-5-5

tests/persistedFieldContract.test.js

@@ -722,6 +722,28 @@ describe("the base profile the sweep corrupts", () => {
     }
 });
 
+// Home, AddressDetail and AddressToken load their transactions inside a catch
+// that only logs, so a boot that fails there still renders the view and passes
+// the tests above while none of that code runs.
+describe("the base profile loads transactions", () => {
+    for (const view of ["main", "address", "address-token"]) {
+        test(`on ${view} without logging a failure`, async () => {
+            const consoleError = jest.spyOn(console, "error");
+            try {
+                await bootPopup(restoringOnto(view));
+                const failures = consoleError.mock.calls
+                    .map((args) => args.join(" "))
+                    .filter((line) =>
+                        /loadHomeTxs failed|loadTransactions failed/.test(line),
+                    );
+                expect(failures).toEqual([]);
+            } finally {
+                consoleError.mockRestore();
+            }
+        });
+    }
+});
+
 // A field the ROUTER itself reads — the two it gates on and the two
 // hasValidAddress() indexes with. A hostile value in one of these legitimately
 // changes which view renders, so each gets its own boot per view and is held