Update epic cache counts on project/group deletion

What does this MR do and why?

When issue's count or weight is changed for an epic, we update its cached values. These cached values are sum of both direct epic's issues and also sub-epic's issues.

Because we want to include subepics weights/counts too, when cached value is changed we propagate this change to all epic ancestors. This is achieved by scheduling cache update for epic's parent in epic's after_commit callback.

Related to #356683 (closed)

DB changes:

• queries to get impacted epics when destroying group or project - !90615 (comment 1000841520) and !90615 (comment 1000999580)
• queries to get epic's cached sum/counts - !90615 (comment 1004585335) and !90615 (comment 1004589231)

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

ee/app/models/ee/epic.rb

@@ -342,8 +342,6 @@ def search(query)
       end
 
       def ids_for_base_and_decendants(epic_ids)
-        return self.class.none unless parent_id
-
         ::Gitlab::ObjectHierarchy.new(self.id_in(epic_ids)).base_and_descendants.pluck(:id)
       end
 
@@ -559,6 +557,8 @@ def level_depth_exceeded?(parent_epic)
     private :level_depth_exceeded?
 
     def base_and_ancestors
+      return self.class.none unless parent_id
+
       hierarchy.base_and_ancestors(hierarchy_order: :asc)
     end