Not able to override keyValueMappingContext

[berickus]

Due to the fact that the RedisEnhancedMappingContext is set as @primary, even when having your own RedisMappingContext like it is done in the unit test, it is not respected and a custom key space resolver is never used.

My config and bean which is never used.
`@Configuration
public class RedisKeyspaceConfig {

@Bean
public RedisMappingContext customKeyValueMappingContext(@Qualifier("redisEnhancedMappingContext") RedisMappingContext mappingContext,
                                                  RedisConfigProperties config,
                                                  Tenant tenant) {
    mappingContext.setKeySpaceResolver(type -> RedisUtils.getKeyspace(type, config, tenant.getName()));
    return mappingContext;
}

}`

Also this way it does not work:
`@Configuration
public class RedisKeyspaceConfig {

@Bean
public RedisMappingContext customKeyValueMappingContext(RedisConfigProperties config,
                                                  Tenant tenant) {
    RedisEnhancedMappingContext mappingContext = new RedisEnhancedMappingContext();
    mappingContext.setKeySpaceResolver(type -> RedisUtils.getKeyspace(type, config, tenant.getName()));
    return mappingContext;
}

}`

[bsbodden]

Fix coming. The Solution:

• Added @ConditionalOnMissingBean(name = "redisEnhancedMappingContext") to the default bean
• Kept @primary for backward compatibility
• This allows users to provide their own mapping context bean without bean definition conflicts

How Users Can Now Override:

  @Bean(name = "redisEnhancedMappingContext")
  @Primary
  public RedisEnhancedMappingContext customMappingContext() {
      RedisEnhancedMappingContext context = new RedisEnhancedMappingContext();
      context.setKeySpaceResolver(type -> "custom:prefix:" + type.getSimpleName());
      return context;
  }