The number of dropped parent transactions in the test_max_disconnect_pool_bytes test was hard-coded to 2.
This happens to work fine on 64-bit for now. However, it seems to fail on 32-bit (https://github.com/bitcoin/bitcoin/issues/34108).
I don’t think we care about the exact number, as long as it is at least 1.
So hard-code 1 for an initial sanity check, and then calculate the exact value at runtime via len(mempool) // 2.
Also, enable the functional tests in 32-bit CI, to confirm the regression test.