Ignore @RequestMapping related beans with functional web apps

[sdeleuze]

After a dedicated discussion with Spring Framework team about enabling or not functional only web configuration, it seems it is not going to happen in Spring Framework 5.3 timeframe, it raises too much open questions and seems a better fit for Spring Framework 6.

So my proposal is to perform a build-time analysis of the application and ignore beans like RequestMappingHandlerMapping and other annotation based ones when no @Controller and @RequestMapping are found, and when actuators are not used.
Notice the actuator efficiency will be explored and discussed as part of spring-attic/spring-native#259. I think there is also a point related to Boot error handling potentially.

It should allow removal of explicit configurations without a footprint regression in our GraalVM native support. This would also remove our last blocking point on spring-projects-experimental/spring-fu#273.

[dsyer]

This is implemented (for now) as a flag spring.native.remove-request-mapping-support (see c9225a1). The func and tunc samples still have selected autoconfigs, but none of them is customized now, and they would work with @SpringBootApplication if anyone needed that.