Should DrillSidewaysQuery BulkScorer leverage scoreSuppliers of the base query and dimensions?

### Description

When DrillSidewaysQuery creates a BulkScorer, it directly calls `#scorer` on the base query and each drill-down dim. This means the drill-down dims are not able to optimize based on leadCost, even though there essentially _is_ a lead clause (the base query). This can be particularly harmful for things like `IndexOrDocValuesQuery`.

Start at DrillSidewaysQuery's BulkScorer creation and inspect how it calls #scorer on the base query and drill-down dimensions. Review the scoreSuppliers and leadCost APIs, then verify that the dimensions can use the base query as a lead clause without changing existing behavior.

Written by the indexing model from the issue text.