fix(retrieval): improve mime type detection and fix async embed of multimodal embedding
Refs: #247
Co-authored-by: SushiNinja<jin.huang2@h-partners.com>
# message auto-generated for no-merge-commit merge:
!282 merge multimodal-embedding-fix into develop
fix(retrieval): improve mime type detection and fix async embed of multimodal embedding
Created-by: SushiNinja
Commit-by: SushiNinja
Merged-by: openJiuwen-bot
Description: <!-- Thanks for sending a pull request! Here are some tips for you:
1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md
2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible.
-->
**What type of PR is this?**
<!--
Choose one label from bug, task, feature and refactor, and replace <label> below the comment block.
If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature.
-->
/kind bug
**What does this PR do / why do we need it**:
- MultimodalDocument class used file extension as mime type, which would be incorrect for cases like mp3 files, which is audio/mpeg instead of audio/mp3.
- In VLLMEmbedding.embed_multimodal method, the last line did not enclose await self._get_embeddings(None, **kwargs) within a bracket, led to indexing failure.
**Which issue(s) this PR fixes**:
<!--
*Automatically closes linked issue when PR is merged.
Usage: Fixes #<issue number>, or Fixes (paste link of issue).
-->
Fixes [#247](https://gitcode.com/openJiuwen/agent-core/issues/247) [#248](https://gitcode.com/openJiuwen/agent-core/issues/248)
**What scenarios were tested, and what were the verification results（Function, performance, reliability, etc.）**：
* Need to describe clearly
**Self-checklist**:（**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**）
+ - [ ] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised
+ - [ ] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded.
+ - [ ] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR.
+ - [ ] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed.
+ - [ ] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner.
<!-- **Special notes for your reviewers**: -->
<!-- + - [ ] Whether it causes forward compatibility failure -->
<!-- + - [ ] Whether the dependent third-party library change is involved -->
See merge request: openJiuwen/agent-core!282