🔐 feat: Implement Allowed Action Domains

[danny-avila]

Summary

Relevant Docs PR: LibreChat-AI/librechat.ai#182

I added support for allowed action domains, refactored domain checking functions, fixed typedef naming issues, updated the data provider version to 0.7.62, and improved typing in RequestExecutor.

• Implemented allowed action domains feature by adding isActionDomainAllowed and isEmailDomainAllowed functions in api/server/services/domains.js.
• Updated middleware checkDomainAllowed and services AuthService to use isEmailDomainAllowed instead of isDomainAllowed, ensuring consistent domain validation.
• Modified ActionService, ToolService, and related routes to check if action domains are allowed before processing actions.
• Added comprehensive tests for domain validation in domains.spec.js and updated existing tests accordingly.
• Removed isDomainAllowed.js and its tests, consolidating domain checks into domains.js.
• Fixed typedef naming by renaming TAgentsEndpoint to TAssistantEndpoint in api/typedefs.js for consistency.
• Updated librechat-data-provider package version to 0.7.62 in packages/data-provider/package.json.
• Improved typing in RequestExecutor class in packages/data-provider/src/actions.ts.

Change Type

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

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.