Don't notify cache about nonces; pass the account nonce provider, instead

[andreibancioiu]

Reasoning behind the pull request

• This is an improvement upon Mempool: improve selection algorithm #6581.
• In certain exotic cases, concurrent notifications about account nonces might have lead the mempool to hold stale account nonces (very minor issue, but still an issue).
• The flow of forgetting all account nonces after reverting a block is suboptimal (and somehow over-engineered).

Proposed changes

• TODO: maybe also drop txs.accountTxsShards?
• Don't be notified about account nonces, don't store them; get them at selection-time mx-chain-storage-go#57
• Also merged this one (PR was previously lost): Optimization: encode hash to hex only on log TRACE level set #6338

Testing procedure

Pre-requisites

Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:

• was the PR targeted to the correct branch?
• if this is a larger feature that probably needs more than one PR, is there a feat branch created?
• if this is a feat branch merging, do all satellite projects have a proper tag inside go.mod?