Spring's configuration class processor provides callbacks for the common BeanClassLoaderAware, BeanFactoryAware, EnvironmentAware, and ResourceLoaderAware contracts, as known from the core BeanFactory creation algorithm. However, its callback order differs from the core BeanFactory for historic reasons: Let's finally align these for 4.3.3, since there are no side effects to expect beyond Boot (which we have immediate CI tests for).
Also, ComponentScanBeanDefinitionParser a.k.a. <context:component-scan> does not provide any such callbacks for XML-defined TypeFilter class names. Let's close that gap as well.