fix: Workaround for repeating logIndex

[nikitosing]

Motivation

sometimes different ETH JSON RPC clients returns bugged response with duplicated logIndex within block or even transaction.

Changelog

• Set new LogIndexes if logIndex is not unique within a block
• Create a migration in order to apply fix to already imported logs, token transfers and token instances

Checklist for your Pull Request (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 docs repository.
• If I added/changed/removed ENV var, I submitted a PR to docs repository to update the list of env vars and I updated the version to master in the Version column. If I removed variable, I added it to Deprecated ENV Variables page. After merging docs PR, changes will be reflected in these pages.
• If I added new DB indices, I checked, that they are not redundant, with PGHero or other tools.
• If I added/removed chain type, I modified the Github CI matrix and PR labels accordingly.