🚀 feat: Implement S3 integration for file handling and image uploads

[rubentalstra]

Summary

Closes: #3373
Closes: #2898

Docs: LibreChat-AI/librechat.ai#256

This pull request introduces support for AWS S3 as a file storage option in addition to Firebase. The key changes include adding the necessary configurations, dependencies, and methods to handle file operations with S3.

AWS S3 Integration:

• .env.example: Added environment variables for AWS S3 configuration, including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, and AWS_BUCKET_NAME.
• api/package.json: Added dependencies for AWS S3 client and presigner.
• api/server/services/AppService.js: Updated to initialize S3 based on the file strategy configuration. [1] [2]
• api/server/services/Files/S3/initialize.js: Created a module to initialize the AWS S3 client.

File Operations:

• api/server/services/Files/S3/crud.js: Implemented CRUD operations for S3, including methods to upload, retrieve, and delete files.
• api/server/services/Files/S3/images.js: Added functions to handle image-specific operations, such as resizing and uploading images to S3.
• api/server/services/Files/S3/index.js: Consolidated S3-related modules for easier imports.

Strategy Integration:

• api/server/services/Files/strategies.js: Integrated S3 as a file storage strategy, adding corresponding functions for file handling. [1] [2] [3]

UI Integration:

• client/src/components/Chat/Input/Files/SourceIcon.tsx: Updated the SourceIcon component to support S3 as a file source.

Configuration:

• librechat.example.yaml: Added an example configuration for selecting the file strategy (S3 or Firebase).

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.

[rubentalstra]

for reference:
#2898 (comment)