Handle various indexer fetchers errors in setup with non-archive node

[vbaranov]

Motivation

Multiple errors if run Blockscout with non-archive Ethereum node

Changelog

Checklist for your Pull Request (PR)

Catching of various errors

• 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 d9304c03f8573aebd4286c86f6a461515ef2d578-PR-3327

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+3.2%) to 74.52%

---

Totals
Change from base Build 698622d362182b8ef6580edd42694891a7eb0d92:	3.2%
Covered Lines:	1980
Relevant Lines:	2657

---

💛 - Coveralls