Expand split spring.autoconfigure.exclude entries for Spring Boot 4.0

Spring Boot 4.0 split several auto-configurations across per-technology modules, so that what one class configured in 3.5 is now configured by two or more independently activating classes. An application excluding the old class keeps only part of it disabled after the upgrade. One-to-one relocations need no recipe of their own: ChangeType and ChangePackage already rewrite fully qualified names in application.properties and application.yaml through org.openrewrite.trait.Reference. A Reference renames to a single name, however, so one-to-many splits are out of its reach. This recipe expands them into all of their successors, as derived from the AutoConfiguration.imports files of Spring Boot 3.5 and 4.0. Excluding a class that is not on the classpath is ignored by Spring Boot, so successors that an application does not use are harmless.