Reschedule epic cache count migration

What does this MR do and why?

Re-enqueues (again) cached counts update. After disabling delayed data_consistency for the worker (!104948 (merged)), new inconsistencies should not be added anymore.

The remaining mismatches are perhaps caused by having invalid cached count set for a sub-epic from previous time (then this invalid sub-epic time is used when counting parent epic cached counts so it causes that parent epic cached counts are invalid too).

Related to #378907 (closed)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

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.