Set infinity timeout and increase cache invalidation period for counters on the main page

[vbaranov]

Motivation

Default cache invalidation interval is too small for counters on the main page and request is dropped after 1 minute

Changelog

Increase default cache invalidation interval up to 15 minutes, set an infinite timeout for counters queries.

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 14466f5390c0521b3c08e080118ef2373efb63bf-PR-3446

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.8%) to 67.433%

---

Files with Coverage Reduction	New Missed Lines	%
lib/block_scout_web/controllers/chain/market_history_chart_controller.ex	1	78.57%

Totals
Change from base Build e0b276e1113fb0c69bc1400254596cbfa0e53fae:	0.8%
Covered Lines:	2054
Relevant Lines:	3046

---

💛 - Coveralls