Less invasive dependencies in starter/autoconfigure

[stengvac]

Hello,

in our project we use spring boot and this nice lib for GQL with microservice architecture. Last few days, I am trying to improve start time and test start time of our apps mainly by spring context reduction (less starters, remove not needed libs etc). This bring me here, because a lot of spring boot libs came as dependencies from this lib and we do not use them, but still we get them on class path.

I would welcome split of graphql-spring-boot-autoconfigure to more specialized autoconfigs if possible - each bringing only libs required for its functionality - developers has to decide which stack they want to use not autoconfig.

Possible split: servlet-autoconfiguration webflux-autoconfiguration websocket-autoconfiguration

starer could contains all of them, but devs can pick if they want.

Possible libs for overall removal: org.springframework.boot:spring-boot-starter-validation - used to validate properties - may not be needed in target project at all.

Thx for consideration,

I can help with the work if you need - but I am Kotlin dev :).