storage: Push CategoryMembershipChangeJob in ChangeTrackingEventIngress

Why:

- CategoryMembershipChangeJob is currently enqueued in
  DerivedPageDataUpdater.
- This job is responsible for creating RC entries for category
  membership changes that resulted from an edit, so it is semantically a
  better fit for ChangeTrackingEventIngress instead.
- Idf6625d3e737e4a225648b0fd81cc929b095d315 unintentionally changed the
  logic to enqueue this job for both direct content changes and
  reconciliation requests, rather than only direct content changes.
  Since the job creates RC entries, it should only be enqueued
  as a result of direct content changes.

What:

- Move the logic of enqueueing CategoryMembershipChangeJobs into
  ChangeTrackingEventIngress.
- Only enqueue CategoryMembershipChangeJobs for direct content changes
  and update tests accordingly.
- Resolve the old TODO of making this logic MCR-aware by checking
  whether any changed content slot supports categories as a precondition
  of enqueueing the job, rather than only checking the main slot.

Bug: T390636
Change-Id: Icfe33ccc6cfa391e65ecae21d8c1d575dc247ee3

0 files changed, 0 insertions, 0 deletions