Take into account batch ERC-1155 transfers while paginating token tra…

[nikitosing]

…nsfers

Close #6919
Close #6841
Close #6842

Changelog

• Refactor http requests logger: Now api, api_v2 and block_scout_web logs saved separately
• Pagination for token transfers takes into account batch ERC-1155 transfers (+ squashes the same token ids)
• Add /smart-contracts/counters
• Refactor functions such as: query_function_with_names, read_only_functions, read_only_functions_required_wallet and some others in order to avoid fetching the same smart contract several times from a DB
• Redirect all the DB read interaction from the API v2 to the read replica

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