Invalidate cache for issue and MR counters separately

What does this MR do?

Invalidate cache for issue and MR counters separately. This saves us some resources.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ce/issues/31926 and https://gitlab.com/gitlab-org/gitlab-ce/issues/14054

changed title from Invalidate cache for issue and MR counters more separately to Invalidate cache for issue and MR counters separately

assigned to @rymai

added ~874211 backstage labels

@vsizov Thanks, looks good to me!

approved this merge request

merged

mentioned in commit d0db4080

mentioned in issue #32415 (moved)

resolved all discussions

mentioned in merge request !11736 (merged)

mentioned in commit 04ba6ae5

mentioned in issue #33450 (closed)