fix: Tx incorrect status

[boecklim]

Description of Changes

Provide a brief description of the changes you've made.

Testing Procedure

• I have added new unit tests
• All tests pass locally
• I have tested manually in my local environment

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have updated CHANGELOG.md with my changes

[shotasilagadzetaal]

So, as I was saying there still is case where we assign rejected status but transaction gets mined eventually.

Imagine we submit chained transaction and for some transactions they don't see parent yet in mempool so we receive ORPHANED status.

Now we do this logic ⬆️ and before we started this check those parent transactions got mined in a new block. So those input transactions now have txInfo.BlockHash != "" || txInfo.BlockHeight > 0 so we assign REJECT status to this one but in fact it will be mined (probably in the next block).

I admit this case is pretty rare but that's why I didn't like the approach because there is the case when we tell user that transaction is rejected but it gets mined eventually which is very bad.