Fix procedure of marking internal transactions as failed

[vbaranov]

Motivation

If a block has multiple transactions and block's first transaction is failed, Blockscout marks all internal transactions in that block as failed too even if their parent transactions are not failed.

Changelog

Fix function of searching failed parent trace to mark child traces as failed.

Checklist for your Pull Request (PR)

• I added an entry to CHANGELOG.md with this PR
• If I added new functionality, I added tests covering it.
• If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
• I checked whether I should update the docs and did so by submitting a PR to https://github.com/blockscout/docs
• If I added/changed/removed ENV var, I submitted a PR to https://github.com/blockscout/docs to update the list of env vars at https://github.com/blockscout/docs/blob/master/for-developers/information-and-settings/env-variables.md and I updated the version to master in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.
• If I add new indices into DB, I checked, that they are not redundant with PGHero or other tools

[coveralls]

Pull Request Test Coverage Report for Build 366363715d6e22d04d08fa6cb55c0c9529ab8ca8-PR-3401

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.9%) to 67.677%

---

Files with Coverage Reduction	New Missed Lines	%
test/block_scout_web/features/pages/chain_page.ex	1	90.0%

Totals
Change from base Build 6af67adf73b30e3ca06e11490c72b2df8df93dc5:	-0.9%
Covered Lines:	2054
Relevant Lines:	3035

---

💛 - Coveralls