feat: itest: force PoSt more aggressively around deadline closure

[arajasek]

Related Issues

A class of tests have been flaking due to PoSts not getting in during a deadline, leading to all power in the network disappearing (example here). This occurs despite the "force post" functionality that is intended to avoid this.

Proposed Changes

More aggressively block and force post (within 5 epochs of the deadline closing).

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green