📦 refactor: Move DB Models to @librechat/data-schemas

[rubentalstra]

Summary

This pull request includes several changes to the api/models directory to improve the codebase by updating schema imports and type definitions. The most important changes involve replacing local schema imports with imports from the @librechat/data-schemas package and updating type definitions in the api/models/File.js and api/models/Project.js files.

Schema Import Updates:

• api/models/Action.js: Updated actionSchema import to use @librechat/data-schemas.
• api/models/Agent.js: Updated agentSchema import to use @librechat/data-schemas.
• api/models/Assistant.js: Updated assistantSchema import to use @librechat/data-schemas.
• api/models/Balance.js: Updated balanceSchema import to use @librechat/data-schemas.
• api/models/Banner.js: Updated bannerSchema import to use @librechat/data-schemas and added mongoose import.

Type Definition Updates:

• api/models/File.js: Updated type definitions from MongoFile to IMongoFile for various methods. [1] [2] [3] [4] [5] [6]
• api/models/Project.js: Updated type definitions from MongoProject to IMongoProject for various methods. [1] [2] [3] [4] [5] [6]

Other Notable Changes:

• api/models/ConversationTag.js: Updated conversationTagSchema import to use @librechat/data-schemas and added mongoose import.
• api/models/Prompt.js: Updated promptGroupSchema and promptSchema imports to use @librechat/data-schemas and added mongoose import.
• api/models/Role.js: Updated roleSchema import to use @librechat/data-schemas and added mongoose import.
• api/models/Session.js: Updated sessionSchema import to use @librechat/data-schemas.
• api/models/Share.js: Updated shareSchema import to use @librechat/data-schemas and added mongoose import.
• api/models/Token.js: Updated tokenSchema import to use @librechat/data-schemas.

Change Type

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Testing

Please describe your test process and include instructions so that we can reproduce your test. If there are any important variables for your testing configuration, list them here.

Test Configuration:

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
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes
• Any changes dependent on mine have been merged and published in downstream modules.
• A pull request for updating the documentation has been submitted.