Skip pseudo bean definition registration during AOT processing

Prior to this commit, AOT processing failed for tests that made use of
the Bean Override feature to "override" a nonexistent bean. The reason
is that we register a "pseudo" bean definition as a placeholder for a
nonexistent bean, and our AOT support cannot automatically convert that
"pseudo" bean definition to a functional bean definition for use at AOT
runtime.

To address that, this commit skips registration of "pseudo" bean
definitions during AOT processing, and by doing so we enable the JVM
runtime and AOT runtime to operate with the same semantics.

See gh-32933

spring-test/src/test/java/org/springframework/test/context/aot/AotIntegrationTests.java

@@ -155,7 +155,6 @@ class AotIntegrationTests extends AbstractAotTests {
 		runEndToEndTests(testClasses, false);
 	}
 
-	@Disabled("Comment out to run Bean Override integration tests in AOT mode")
 	@Test
 	void endToEndTestsForBeanOverrides() {
 		List<Class<?>> testClasses = createTestClassScanner()