Fix db pool size exceeds Postgres max connections

[vbaranov]

Motivation

Setting pool size=50 leads to number of connections to DB > 200.

Changelog

Exclude repos which are supposed to be operated by the same DB (like RSK and PolygonEdge repos) for the application children except tests. Currently, all pool sizes are concatenated, resulting high total pool size.

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