mpool: fix: data race when adding messages

[snissn]

Related Issues

#10755

Proposed Changes

Remove cache hacks and change actor look up from GetActorAfter to GetActorBefore

Additional Info

This drop support for sending messages from an account immediately after creating it

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

[Stebalien]

Ok, so, I was wrong. checkBalance calls GetActorAfter (through getStateBalance) as well so warming the cache is still effective. We could try to switch that check to GetActorBefore as well, but I'm even less sure of the potential downsides...

[snissn]

Closing this PR for new PR: #10771

I added RLocks around the getStateNonce call in the new PR