Bump submodules/btracker to balance_tracker's integration tip: the pinned 877d7ec predates 1.28.8 and carries none of #68/#69/#72

Problem

submodules/btracker on aidev/integration pins balance_tracker 877d7ec, a 1.28.8-rc2-era commit older than the 1.28.8 tag (451a6924). A block explorer built from this branch therefore embeds a balance_tracker without any of its recent fixes:

  • balance_tracker#68 (closed): per-row plpgsql calls, the O(n²) recursive gap-fill and the plan-cache traps in five read endpoints. On a full-scale node, vesting-history goes from 83 ms to 1.1 ms; aggregated-history daily full history from 148 ms to 14 ms; transfer-statistics hourly from 924 ms to 304 ms; vesting-stats 2.5–3× faster; get_account_balances first calls of a session from 9.6 ms to 1.1 ms.
  • balance_tracker#69 (closed): insert-only autovacuum reloptions and a post-finalize VACUUM (FREEZE, ANALYZE) request for the history tables, so they keep a visibility map.
  • balance_tracker#72 (closed): its maintenance test, made aware of HAF's vacuum request kinds.

These fixes were measured with the block explorer from this branch combined with balance_tracker's integration branch. The block explorer as pinned does not include them. In particular, /accounts/{a} calls btracker_endpoints.get_account_balances, so the fix for its first-call planning cost only reaches block explorer users once the submodule moves.

Change

  • Move submodules/btracker to balance_tracker's current aidev/integration tip (9440c7dc5b71f895c83a6f5f0ee6c6e1b60ef6ea at the time of filing). It contains #68 (closed), #69 (closed) and #72 (closed).

  • Check that the block explorer's embedding still works with that version:

    • the block explorer calls balance_tracker's finalize_massive_sync_before_forking() itself before switching both contexts to forking;
    • #69 (closed) adds reloptions and a request_history_tables_freeze() call in finalize;
    • #68 (closed) changes function signatures and bodies in btracker_backend.

    Adjust any block explorer call site or install step that relies on the old behaviour.

  • Leave submodules/reptracker as it is.

Acceptance

  • The quick, full and baseline slots pass with the new pin, including install, sync, regression and tavern against the shared HAF.
  • After install and sync, hafbe_bal.account_balance_history and hafbe_bal.account_vesting_history carry #69 (closed)'s insert-only reloptions. On a HAF with request kinds, finalize queues one 'freeze' request per table and no 'full' request.
  • /accounts/{a} returns byte-identical output before and after the bump on the tavern accounts.