Repartitioning object catalog after spatial filtering to improve speed

When selecting only a spatial subset of data from object table, and then asking for the data from the source table currently we would pull all the data from the source partitions which correspond to partitions selected in the object table. Because the object table partitioning is much coarser, we are pulling data from many sources partitions which would not necessarily in the original spatial query.

The idea is to not have to load the data from the partitions in the source table that are not selected. When the spatial filter is performed on the object table we could repartition the resulting object table to a higher order.

Start by tracing the spatial-filtering path from the object table to source-table loading and inspect how selected partitions are represented. Define done as preventing source partitions outside the spatial result from loading while preserving the requested data and query behavior.

Written by the indexing model from the issue text.