✨ feat: Implement basic Group Functionality

[rubentalstra]

Summary

This pull request includes significant changes to the group management and OpenID strategy, as well as updates to the client-side model specifications handling. The most important changes include the introduction of group management methods, enhancements to OpenID strategy for group handling, and updates to the client-side model specifications to respect user group permissions.

Group Management Enhancements:

• api/models/Group.js: Added the Group model definition using Mongoose.
• api/models/groupMethods.js: Implemented methods for creating, updating, finding, and deleting groups, including checks for user assignments and overriding deletions.
• config/assign-group.js: Created a script to assign a group to a user via CLI with necessary validations and error handling.
• config/create-group.js: Added a script to create a new group with options for local or OpenID group types.

OpenID Strategy Enhancements:

• api/strategies/openidStrategy.js: Introduced functions to extract roles from tokens and update user groups based on these roles, integrated into the OpenID strategy setup. [1] [2] [3] [4] [5] [6]
• api/strategies/openidStrategy.spec.js: Mocked findGroup method for testing the OpenID strategy.

Client-Side Model Specifications:

• client/src/components/Chat/Menus/Models/ModelSpecsMenu.tsx: Filtered model specifications based on user groups, ensuring only allowed specs are displayed. [1] [2] [3] [4]
• client/src/components/Chat/Menus/Models/ModelSpec.tsx: Added support for displaying badges on model specifications.

Additional Changes:

• api/models/index.js: Included the Group model in the exports. [1] [2]
• librechat.example.yaml: Added example configuration for model specifications with group assignments.

Change Type

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

Testing

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.

[maxesse]

Hi @rubentalstra here's the group-based modelspecs filtering feature I developed on my fork: https://github.com/maxesse/LibreChat/tree/feat/group-based-modelspecs-access

[rubentalstra]

---

---

[rubentalstra]

Updated to use the new data-schemas package ✅