fix: add supported file loaders to detect the override file from upsert API

[prd-hoang-doan]

Issue:

• Ticket: File Loader Not Picking Up Provided File(s) from Request - After Upgrading from 3.0.4 to 3.1.1 #6102

Root Cause:

• Pull Request: Fix Paramater Override Bypass #5667
• Although the user enable override configuration on File Loader, but they can use the file from request to upsert data into vector db.

Changes

• Add SUPPORTED_FILE_LOADERS (source) to detect the overrideConfig from API: vector/upsert/:uuid
• Get the latest file from overrideConfig instead of using the default file name in Chatflow in Upsert History

Testing

• Creating the Chatflow with initial file (test3.docx)
• Using Upsert API to upload another (test.docx)

create_and_upsert_chatflow.mov

• Verify the Upsert History

check_upsert_history.mov

[gemini-code-assist]

Code Review

This pull request introduces a list of supported file loaders and updates the server utilities to handle file storage overrides during the upsert process. It includes logic to correctly identify filenames from overrides and maps specific file loader parameters to a generic 'files' key for override validation. Feedback indicates that the node type check for file loaders is too restrictive and should be expanded to include specific file types like 'Pdf File'. Furthermore, several naming inconsistencies were identified in the SUPPORTED_FILE_LOADERS list that need to be aligned with the document loader components to ensure overrides function correctly for all file types.