Explicitly set work type when using ReactiveCaching concern
With the work coming together with gitlab-org/gitlab!30212 (merged), we explicitly set some callers of ReactiveCaching
to use self.reactive_cache_work_type = :external_dependency
. If it's not set, it'll automatically fallback to the :default
. The former will pick ExternalReactiveCachingWorker
to enqueue and perform the work, the latter will fallback to the old ReactiveCachingWorker
.
Ideally we should make all callers set the reactive_cache_work_type
, which will give people a chance to think about the work being performed for new users of this concern, enqueuing work to the proper nodes/queues.