PrimaryOnlyService is the way we manage this today, but is missing some things.

One specific request comes from CAR, to preserve lock state between operations, passing locks from one op to the next The specific state requested to be passed is identical to the lock state. in the helper class in SPM-4434.

Note that the unbounded memory usage from repeatedly attaching operations to the same cancelation source is not part of this ticket, but is instead part of our cancelation improvements project.

Split out from SERVER-91662