MemorySegment scorer should ensure that the values is of the correct …

…type (#13423)

This commit updates the MemorySegment scorer so that it ensures the values is of the correct type.

The offset calculations for vectors in RandomAccessQuantizedByteVectorValues will be different than that of non-quantized. We can generalise the implementation for quantized vectors later, but for now, passing a quantised values indicated bug in wrapping or delegation.

lucene/core/src/java21/org/apache/lucene/internal/vectorization/Lucene99MemorySegmentFlatVectorsScorer.java

@@ -23,6 +23,7 @@
 import org.apache.lucene.util.hnsw.RandomAccessVectorValues;
 import org.apache.lucene.util.hnsw.RandomVectorScorer;
 import org.apache.lucene.util.hnsw.RandomVectorScorerSupplier;
+import org.apache.lucene.util.quantization.RandomAccessQuantizedByteVectorValues;
 
 public class Lucene99MemorySegmentFlatVectorsScorer implements FlatVectorsScorer {
 
@@ -39,6 +40,8 @@ private Lucene99MemorySegmentFlatVectorsScorer(FlatVectorsScorer delegate) {
   public RandomVectorScorerSupplier getRandomVectorScorerSupplier(
       VectorSimilarityFunction similarityType, RandomAccessVectorValues vectorValues)
       throws IOException {
+    // a quantized values here is a wrapping or delegation issue
+    assert !(vectorValues instanceof RandomAccessQuantizedByteVectorValues);
     // currently only supports binary vectors
     if (vectorValues instanceof RandomAccessVectorValues.Bytes && vectorValues.getSlice() != null) {
       var scorer =
@@ -68,6 +71,8 @@ public RandomVectorScorer getRandomVectorScorer(
       byte[] queryVector)
       throws IOException {
     checkDimensions(queryVector.length, vectorValues.dimension());
+    // a quantized values here is a wrapping or delegation issue
+    assert !(vectorValues instanceof RandomAccessQuantizedByteVectorValues);
     if (vectorValues instanceof RandomAccessVectorValues.Bytes && vectorValues.getSlice() != null) {
       var scorer =
           Lucene99MemorySegmentByteVectorScorer.create(