Fix QN sync after transactions

[thesan]

Bug identified by @kdembler:

Context

After most transactions Pioneer waits for the block that includes the transaction to be processed by the QN to complete the flow and re-fetch data. It does so by checking the queryNodeState QN subscription. However it checks queryNodeState.indexerHead instead of queryNodeState.lastCompleteBlock to query the hash that it compares to the transaction hash.

As a result:

• When the transaction hash is actually found: the block hasn't yet been processed by the QN, so the new data will be missing after re-fetching the queries.
• When queryNodeState.indexerHead is already ahead of the transaction block, the hash won't be found and the user will be asked to wait until a timeout happens.

Scope

1. Checking for queryNodeState.lastCompleteBlock instead of queryNodeState.indexerHead.
2. Account for potential subscription misses by checking for the block height associated with the transaction hash and then waiting for queryNodeState.lastCompleteBlock to be equal or greater than this block height.

[thesan]

Solved on the backend branch in #4579