The issue that error is reported when the vector database is configured to PGVECTO_RS is fixed

[limengning]

Summary

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Tip

Close issue syntax: Fixes #<issue number> or Resolves #<issue number>, see documentation for more details.

Screenshots

Before	After
...	...

Checklist

Important

Please review the checklist below before submitting your pull request.

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[bowenliang123]

-1 for this PR.
The value of PgVecto RS for VECTOR_TYPE has been pinned as pgvecto_rs, which brings breaking changes for existed users if this value is changed. As for the name PGVECTO_RS in code, it follows the python code sytle preferring _ than -. There's not urgant reason to force alignment in these two concepts.

If pgvecto_rs config value somehow shows on docs, please fix the docs instead.