Goal :

Today the content counting on capsules which is then displayed on the UI is a global task that updates content counts on all of the capsule. We should have some granularity on the task so we can cut down on the time to run this task. Please note that this task is run on every capsule sync asynchronously but can cause bottlenecks if there are network constraints between server and capsule.

Granularity here means updating content counts not for the whole capsule, but for one content view and/or lifecycle environment at a time.

Acceptance Criteria:
1. The system should be able to update content counts for a specific content view and/or lifecycle environment, rather than the entire capsule, during the task execution.

2. The content counting task must continue to run asynchronously for each specified content view and lifecycle environment, without requiring a global update across all capsules.

3. Complete capsule sync should continue to run the content count globally and asynchronously.

4. Refresh count action on the UI should be able to target individual env/cv for content counting.
5. Optimized sync should only update counts if contents are actually changed.