fix(schema): correctly cache text indexes as 'text' not 1

[vkarpov15]

Summary

Spotted an inconsistency in how text indexes are handled in schema.indexes(). schema.indexes() incorrectly modifies state that future calls depend on, so without this fix, the first schema.index() call will correctly return { content: 'text' } but the 2nd would return { content: 1 }

Examples

[Copilot]

Pull Request Overview

This PR fixes a bug where schema.indexes() incorrectly cached text indexes. The issue caused subsequent calls to return { content: 1 } instead of the correct { content: 'text' } because the function was modifying the original index object instead of creating a copy.

• Fixed mutation of cached index objects by creating a shallow copy of the options object
• Added test coverage to verify text indexes are correctly retained across multiple schema.indexes() calls

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
lib/helpers/schema/getIndexes.js	Added object spread operator to create a copy of the index options, preventing mutation of cached data
test/schema.test.js	Added test case verifying that text indexes maintain their 'text' type across multiple schema.indexes() calls

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}