fix(embed): give warning when embeder and vectoerdb are not the same.

[zhougit86]

Description

This PR adds a configuration validation step to check the consistency of vector dimensions. It compares the dimension specified for storage.vectordb with the dimension configured for embedding. If both values are greater than 0 but do not match, the system will log a warning to help users catch potential vector search errors early.

Related Issue

N/A

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test update

Changes Made

• Added a dimension consistency check in OpenVikingConfig.from_dict (openviking_cli/utils/config/open_viking_config.py).
• Added a standard logging.warning output to notify users of dimension mismatches.
• Applied ruff formatting to the modified code blocks to ensure styling compliance.

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested this on the following platforms:
  • Linux
  • macOS
  • Windows

Checklist

• My code follows the project's coding style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings (Note: Added an intentional runtime warning for invalid configs)
• Any dependent changes have been merged and published

Screenshots (if applicable)

N/A

Additional Notes

The warning uses the standard logging module directly to avoid infinite recursion that could occur if get_logger triggers config initialization before the config object is fully loaded.

[github-actions]

Failed to generate code suggestions for PR

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

xiaogang.zhou seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

xiaogang.zhou seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}