Ensure `possible_next_nonce` reports correct value for sponsored txs

There's a report of a possible bug when the API calculates nonces for addresses associated with sponsored transactions. The report indicates the issue may be related to when the mempool is queried for nonces. This needs to be investigated to determine if there is an actual bug. Then the fix is likely straightforward.