Call the API tools directly without using ApiAnalysisApplication

[laeubi]

This replaces ApiAnalysisApplication usage by a more direct approach that do not require us to pass file lists around and directly class the ApiTools.
This is also much more flexible in regard to debugging and additional printouts but still retains that we can consume dynamic implementation from P2 repositories.

Currently this is work-in-progress:

1. For full features we need a solution for the problem described here: [apitools] BaseApiAnalyzer should have a way to discover the source without a java project eclipse-pde/eclipse.pde#785
2. Currently API problems are just printed for demo purpose and feature validation
3. The ApiTools currently determine the profile internally, we should supply the profile generated by Tycho

[github-actions]

Test Results

   561 files  ±0     561 suites  ±0   4h 52m 50s ⏱️ + 30m 49s
   364 tests ±0     358 ✔️ +1    6 💤 ±0  0 ❌ ±0 
1 092 runs  ±0  1 073 ✔️ +1  19 💤 ±0  0 ❌ ±0 

Results for commit 408b95a. ± Comparison against base commit a1c9e4b.

♻️ This comment has been updated with latest results.

[laeubi]

This is ready now and gives much better user feedback. Instead of "ApiApplication failed" and require the user to scan the logs one now will be presented in the error message with the details about the failure:

beside that the API analysis is now faster because we don't need to build / compile the project to perform the API analysis (in this case before 25 seconds now 15 seconds).

This also adds a new parameter "debug" that prints additional information about the used API baseline:

<plugin>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>tycho-apitools-plugin</artifactId>
	<configuration>
		<debug>true</debug>
	</configuration>
</plugin>

[github-actions]

💚 All backports created successfully

Status	Branch	Result
✅	tycho-4.0.x

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details