Evaluate performance and usage of epic issues count graphql endpoint

!19450 (merged) introduced graphql API endpoint for getting number of sub-epics and issues. This query is not so cheap (multiple queries, checking permissions), so we should check production performance and evaluate if some additional caching is needed or further optimizations in usage/polling this endpoint by FE is needed.

Related to discussion in !19450 (comment 240538314)