🔧 fix: Apply Mongoose Plugin at Model Creation

[danny-avila]

Summary

I fixed an issue where the mongoMeili plugin was being applied to schemas during schema definition instead of during model creation, which caused problems with the main runtime mongoose instance as is not accessible within the package.

• Moved mongoMeili plugin application from schema definition to model creation in both conversation and message models
• Updated the mongoMeili plugin to accept a mongoose parameter and use proper TypeScript imports instead of direct mongoose imports
• Modified the plugin to use the passed mongoose instance for database operations instead of relying on a global mongoose instance
• Removed the plugin application from the schema files to prevent early binding issues
• Added proper TypeScript types for FilterQuery and Types to improve type safety

Other Changes

• Closes [Bug]: Agent Max Context & Tokens form field cannot be reset #7747
  • Replace useCallback with useMemo for the debounced function to ensure proper stability and typing
  • Add fallback function to prevent undefined setter in debounced function creation
  • Improve numeric conversion logic to handle undefined and empty string values properly
  • Remove unused useDebounceCodeBlock hook from the Artifacts component directory

Change Type

• Bug fix (non-breaking change which fixes an issue)

Testing

The fix was tested by verifying that the mongoMeili plugin now properly uses the main runtime mongoose instance when models are created, preventing connection and schema conflicts.

Test Configuration:

• MongoDB with MeiliSearch integration enabled
• Environment variables MEILI_HOST and MEILI_MASTER_KEY configured
• Multiple mongoose instances in the application

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• My changes do not introduce new warnings
• Local unit tests pass with my changes