Explore additional Spring AOT optimizations on the JVM

Spring AOT is a mandatory step to build a native image for a Spring applications. While adding support for native images, our goal has always been to make this relevant for JVM use cases as well. While we've been focusing on native compatiblity (i.e. RuntimeHints) during the first couple feature release of Spring Framework 6, we'd like to explore JVM use cases and optimize them.

This includes:

• Performance measurement of our AOT-processed BeanFactory, optimizations for straightforward use cases to avoid computing something that can be set at build-time.
• Pragmatic migration of runtime processing to AOT, based on benchmarks. With native constraint out of the picture, we can focus on things we're still doing at runtime that can lead to memory/cpu consumption.

See also:

• #31307