SLING-13050 Include Integration Tests (Single POM)

[stefanseifert]

this is an alternative to #68 - integration the ITs in the impl module, having only a single POM/module.

[stefanseifert]

it seems there is one flaky integration test which i could not reproduce locally so far, but it failed twice in jenkins (and did pass with a re-run in jenkins):

| [ERROR]   InjectorSpecificAnnotationIT.test:61 Model is null

[stefanseifert]

the flakyness problems is likely not related to the actual validation in InjectorSpecificAnnotationIT - it's just the first IT that happened to be executed.

but in the teleporter customizer, we are having an extra check with polling until ModelApdapterFactory component is available and in state=active - so i don't see what might not be ready when the first IT is running:

sling-org-apache-sling-models-impl/src/test/java/org/apache/sling/junit/teleporter/customizers/SM_TeleporterCustomizer.java

Lines 40 to 59 in 4ab1514

	private static final Class[] EXPECTED_COMPONENTS = new Class[] {ModelAdapterFactory.class};
	@Override
	public void customize(TeleporterRule t, String options) {
	final ClientSideTeleporter cst = (ClientSideTeleporter) t;
	cst.setBaseUrl(S.getServerBaseUrl());
	cst.setServerCredentials(S.getServerUsername(), S.getServerPassword());
	cst.setTestReadyTimeoutSeconds(TimeoutsProvider.getInstance().getTimeout(5));
	cst.includeDependencyPrefix("org.apache.sling.models.it.testing");
	// additionally check for the registration of mandatory sling models components
	try (OsgiConsoleClient osgiClient =
	new OsgiConsoleClient(URI.create(S.getServerBaseUrl()), S.getServerUsername(), S.getServerPassword())) {
	for (Class clazz : EXPECTED_COMPONENTS) {
	osgiClient.waitComponentRegistered(clazz.getName(), 20000, 200);
	}
	} catch (ClientException | TimeoutException | InterruptedException | IOException ex) {
	throw new RuntimeException("Error waiting for expected components.", ex);
	}
	}

[stefanseifert]

i'm currently failing to reproduce the flaky test, created a separate branch with running only the ITs and leaving out everything else. also the main branch is file.

so there is some uncovered flakyness - but i think it's fine to merge this PR anyway, so we get a way forwards and apply the same pattern to the other modules with existing ITs as well - sooner or later we will find the root cause.

[sonarqubecloud]

Quality Gate passed

Issues
23 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud