Fix conflicting bean names between @EnableWebSecurity and @EnableWebSocketSecurity

[ngocnhan-tran1996]

I think we should change bean name or use @ConditionalOnMissingBean

Closes #16011

[jzheaux]

Thanks, @ngocnhan-tran1996. Will you please squash your commits and include the needed Closes message at the end? It should look like this:

Resolve Observation Bean Name Collisions

Closes gh-16011

Since this became time-sensitive as we decided to release the fix today, I went ahead and took care of these items. Thanks again, @ngocnhan-tran1996, for the fix!

[gncj]

Even with the fix I'm getting error when moved tthe versions of spring boot to 3.4.1 and spring security to 6.4.2:

---

APPLICATION FAILED TO START

---

Description:

Parameter 0 of method setFilterChains in org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration required a single bean, but 2 were found:
- objectPostProcessor: defined by method 'objectPostProcessor' in class path resource [org/springframework/security/config/annotation/configuration/ObjectPostProcessorConfiguration.class]
- webSocketAuthorizationManagerPostProcessor: defined by method 'webSocketAuthorizationManagerPostProcessor' in class path resource [org/springframework/security/config/annotation/web/socket/WebSocketObservationConfiguration.class]

This may be due to missing parameter name information

Action:

Consider marking one of the beans as @primary, updating the consumer to accept multiple beans, or using @qualifier to identify the bean that should be consumed

[ngocnhan-tran1996]

@gncj

This PR was merged.

You can reach out #16299 or spring-projects/spring-framework#34119

Thanks