refactor: do not export legacyVectors directly

Author: bevzzz

src/collections/configure/index.ts

@@ -15,7 +15,7 @@ import {
 import generative from './generative.js';
 import reranker from './reranker.js';
 import { configure as configureVectorIndex, reconfigure as reconfigureVectorIndex } from './vectorIndex.js';
-import { legacyVectors, multiVectors, vectors } from './vectorizer.js';
+import { multiVectors, vectorizer, vectors } from './vectorizer.js';
 
 import { parseWithDefault } from './parsing.js';
 
@@ -61,9 +61,9 @@ const configure = {
   multiVectors,
   reranker,
   /**
-   * @deprecated Use `vectors` instead.
+   * @deprecated Use `configure.vectors` instead.
    */
-  vectorizer: legacyVectors,
+  vectorizer: vectorizer,
   vectors,
   vectorIndex: configureVectorIndex,
   dataType,
@@ -311,6 +311,6 @@ export {
   tokenization,
   vectorDistances,
   configureVectorIndex as vectorIndex,
-  legacyVectors as vectorizer,
+  vectorizer,
   vectors,
 };

src/collections/configure/vectorizer.ts

@@ -117,10 +117,8 @@ const formatMulti2VecFields = (
 /** Previously all text-based vectorizers accepted `vectorizeCollectionName` parameter, which was meaningless for some modules and caused others to produce confusing results (see details below). Moving forward, we want to deprecate the usage of this parameter.
  *
  * Collections with `vectorizeCollectionName: true` generate embeddings even if they have no vectorizeable properties. This means all generated embeddings would embed the collection name itself, which makes them rather meaningless.
- *
- * @deprecated Use `vectors` instead.
- * */
-export const legacyVectors = {
+ */
+const legacyVectors = {
   /**
    * Create a `VectorConfigCreate` object with the vectorizer set to `'none'`.
    *