Revisit how applicationTaskExecutor is utilized across various Spring integrations

[nosan]

The current setup seems complex and might need reconsideration.

Spring MVC, Spring WebFlux, and Spring GraphQL all rely on a bean named
applicationTaskExecutor. For Spring MVC and Spring WebFlux (spring.threads.virtual.enabled=true), this bean must be of type AsyncTaskExecutor, whereas Spring GraphQL requires a bean of type Executor.

Spring WebSocket and JPA will use an AsyncTaskExecutor if either a single bean of this
type is available or if a bean named applicationTaskExecutor is defined.

I suggest revisiting the WebSocketMessageConverterConfiguration and
JpaRepositoriesAutoConfiguration configurations to align them with Spring MVC,
Spring WebFlux, and Spring GraphQL.

I am uncertain about GraphQL as it uses applicationTaskExecutor but with a different
type.

[mcedeno1]

I would like to learn

[nosan]

I've prepared some changes in my branch main...nosan:44946

---

I still have not decided what type should be used for Spring WebSocket and GraphQL, as both of them can be configured with an Executor.

The current arrangement in the proposed changes is to use Executor for both GraphQL and Spring WebSocket, while AsyncExecutor is used for others. However, all of them require a bean named applicationTaskExecutor.