Add a PostgreSQL memory-usage benchmark for the archive node's database helpers

Long-running archive nodes could grow their PostgreSQL backend memory over time because each database call registered a new server-side prepared statement that lived for the lifetime of the connection. A new benchmark measures that growth and runs in CI, so regressions in archive database memory usage are caught before a release rather than after a node runs out of memory.
