This is a refactoring ticket.

Currently we don't go through the normal query parsing logic of ParsedDelete for IDHACK solution for delete command inside ParsedDelete::parseRequest().

Instead, we manually compose IDHACK plan inside getExecutorDelete(). As part of this process, we figure out the collator to use.

Given that recently timeseries arbitrary updates/deletes project added a collator resolution logic, we should be able to reuse ParsedDelete's expCtx's collator for IDHACK plan too.

Probably we may want to IDHACK eligibility check into ParsedDelete too and add isIDHackEligible() method and only do the final step like creating IDHackStage and generate the IDHACK plan inside getExecutorDelete()