Registration of SecurityFilterChain via WebSecurityCustomizer results in UnreachableFilterChainException

Describe the bug
Spring Security automatically adds a default SecurityFilterChain when no SecurityFilterChain bean has been configured. This conflicts with SecurityFilterChains added via a WebSecurityCustomizer resulting in an UnreachableFilterChainException at application startup because the automatically configured filter chain matches any request.

To Reproduce

@Configuration(proxyBeanMethods = false)
public class SecurityConfiguration {
    
    @Bean
    public WebSecurityCustomizer security(HttpSecurity http) throws Exception {
        http.authorizeHttpRequests(registry -> registry.anyRequest().permitAll());
        var chain = http.build();

        return web -> web.addSecurityFilterChainBuilder(() -> chain);
    }
}

Expected behavior
The default SecurityFilterChain should only be added to the WebSecurity if no SecurityBuilder<? extends SecurityFilterChain> is present after adding all SecurityFilterChain beans and applying all WebSecurityCustomizers.