DenyAllPermissionEvaluator Used As Silent Backup When Two PermissionEvaluator Beans Exist

Describe the bug
When two or more PermissionEvaluator beans are present in an application, Spring seems to silently choose the DenyAllPermissionEvaluator instead of failing to startup due to having duplicate beans.

This feels like a bug, and could have dangerous consequences for enterprises by silently pushing out code to production that seems to build/run as expected, but once an endpoint is hit that calls hasPermission(), it is always denied.

spring-boot team reported it is due to this logic.

To Reproduce
Create two or more PermissionEvaluators in the same project (through an external dependency or otherwise)

Expected behavior
I think Spring should be failing at startup if there are multiple PermissionsEvaluators similar to behavior for other duplicate beans, or otherwise clearly warn developers of the case.

Start in config/src/main/java/org/springframework/security/config/annotation/method/configuration/GlobalMethodSecurityConfiguration.java around line 192, where the issue says the fallback is selected. Trace how multiple PermissionEvaluator beans are resolved and compare that behavior with duplicate-bean handling elsewhere in the project. Done should mean duplicate evaluators no longer fail silently, with startup failure or a clear warning matching the chosen behavior.