MergePolicy "find merges" methods take a MergeTrigger as parameter, except findForcedMerges() and findForcedDeletesMerges(). In my use-case, I could leverage a MergeTrigger in findForcedMerges(), which can be EXPLICIT or MERGE_FINISHED, to differentiate the merge selection between the initial explicit call and the subsequent calls triggered after the first merges.
Should we add a MergeTrigger parameter to all MergePolicy "find merges" methods for consistency? If so, is it an internal or public API? (should this change stay in the main branch only)
