Feat/vector db pgvector

[vaayne]

Description

Support pgvector a new type of vector database.

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update, included: Dify Document
• Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement
• Dependency upgrade

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Local integration tests

Suggested Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
• optional I have made corresponding changes to the documentation
• optional I have added tests that prove my fix is effective or that my feature works
• optional New and existing unit tests pass locally with my changes

[JohnJyong]

hi @vaayne , pls add the integration_tests for the pgvector in the folder 'tests.integration_tests.vdb', thanks

[vaayne]

all done @JohnJyong

[JohnJyong]

This branch has conflicts that must be resolved @vaayne

[JohnJyong]

our db is using the postgresql , the pgvector is using the same volumes path and port with it , it's better to set another folder path and port for pgvector , thanks @vaayne

[vaayne]

All done @JohnJyong

[vaayne]

@JohnJyong Do you have time to review this PR, Thanks

[JohnJyong]

LGTM , thanks for your contribution @vaayne