Modify the $testVectorSearchOptimization extension so it (1) uses get_pipeline_bounds() to derive the effective limit from pipeline bounds and serializes this limit for explain, replacing legacy set_vector_search_limit_for_optimization behavior, and (2) implements a reorder rule that removes a redundant $sort on vectorSearchScore after the extension stage via the new RBR-based rewrite API, while keeping old optimization hooks active behind the new feature flag to validate parity.