fix: GH-3690, enhance RedisVectorStore with RedisVectorStoreBuilderCustomizer

[lanpf]

Description

This PR introduces a generic extension point for customizing VectorStore.Builder via VectorStoreBuilderCustomizer and fixes retrieval failures in RedisVectorStore.

Background

Previously, when using VectorStoreChatMemoryAdvisor with RedisVectorStore and initialize-schema=true, metadata fields like conversationId (used in filterExpression) weren't registered in the Redis schema. This occurred because RedisVectorStoreProperties didn't support setting metadataFields during auto-configuration, causing retrieval failures during similarity search.

Related issue: #3690

Changes

1. Introduces base VectorStoreBuilderCustomizer<T extends VectorStore.Builder<T>> interface
   • Provides extension point for all VectorStore implementations
2. Adds Redis-specific RedisVectorStoreBuilderCustomizer
   • Extends VectorStoreBuilderCustomizer<RedisVectorStore.Builder>
3. Modifies RedisVectorStoreAutoConfiguration
   • Uses RedisVectorStore.Builder as dependency
   • Applies ordered customizers during configuration
4. Includes comprehensive unit tests (special thanks to @Acacian)

New Customization Pattern

Developers can now customize metadata fields non-invasively:

@Bean
public RedisVectorStoreBuilderCustomizer metadataCustomizer() {
    return builder -> builder.metadataFields(
        List.of(RedisVectorStore.MetadataField.tag("conversationId"))
    );
}

Impact

• Enables schema initialization and metadata filtering to work together
• Maintains initialize-schema=true functionality
• Eliminates need for manual RedisVectorStore wiring
• Follows Spring's open/closed principle for extension

Special Thanks

🙌 To @Acacian for test contributions and valuable feedback.

Closes: #3690

Looking forward to your review!

[Acacian]

Thank you for keeping the words you shared earlier. I’ll also keep the words I said before. I appreciate your thoughtfulness.
I hope your contribution will be included in the next release.
Could you please add Closes #XXXX in the PR description to indicate that this issue was resolved by your contribution?
This helps automatically close the issue when the PR is merged and properly credit your work. Thank you!

[lanpf]

Thank you for keeping the words you shared earlier. I’ll also keep the words I said before. I appreciate your thoughtfulness. I hope your contribution will be included in the next release. Could you please add Closes #XXXX in the PR description to indicate that this issue was resolved by your contribution? This helps automatically close the issue when the PR is merged and properly credit your work. Thank you!

Thanks for pointing that out! I've corrected the formatting - the issue reference Closes #3690 is now properly displayed in markdown.

[lanpf]

@ilayaperumalg Could someone approve running CI for this PR?

[lanpf]

@ilayaperumalg Could someone approve running CI for this PR?

@ilayaperumalg Apologies for the oversight—I didn’t have access to my work computer when submitting the PR and forgot to run the code formatting checks. I’ve now resolved the formatting issues using mvn spring-javaformat:apply. Could you please rerun the CI checks? Sorry again for the inconvenience!

[ilayaperumalg]

@lanpf No problem at all. thank you for the follow up and the contribution!

[markpollack]

getting back to this... sorry, catching up.