DO NOT MERGE

[iloveeclipse]

Check if API tools are working in platform UI.

This PR should fail validation because it adds new API with wrong since tag.

See #2430
See #1922

[iloveeclipse]

https://ci.eclipse.org/platform/job/eclipse.platform.ui/job/PR-1922/4/consoleFull

07:49:23.005 [INFO] --- tycho-apitools:4.0.8:verify (verify) @ org.eclipse.ui.workbench ---
07:49:23.007 [INFO] Resolve API baseline for org.eclipse.platform:org.eclipse.ui.workbench:eclipse-plugin:3.133.100-SNAPSHOT with linux/gtk/x86_64
07:50:08.081 [INFO] API Analysis finished in 45 s.
07:50:08.207 [ERROR] [API ERROR] File MANIFEST.MF at line 5: The minor version should be incremented in version 3.133.100, since new APIs have been added since version 3.133.0 (location: /home/jenkins/agent/workspace/eclipse.platform.ui_PR-2439/bundles/org.eclipse.ui.workbench/META-INF/MANIFEST.MF)
07:50:08.235 [WARNING] 1 API problems can't be mapped to the compiler log!

https://ci.eclipse.org/platform/job/eclipse.platform.ui/job/PR-2439/1/consoleFull

11:14:33.401 [INFO] --- tycho-apitools:4.0.8:verify (verify) @ org.eclipse.ui.workbench ---
11:14:33.403 [INFO] Resolve API baseline for org.eclipse.platform:org.eclipse.ui.workbench:eclipse-plugin:3.133.100-SNAPSHOT with linux/gtk/x86_64
11:15:13.323 [INFO] API Analysis finished in 39 s.
11:15:13.391 [ERROR] [API ERROR] File MANIFEST.MF at line 5: The minor version should be incremented in version 3.133.100, since new APIs have been added since version 3.133.0 (location: /home/jenkins/agent/workspace/eclipse.platform.ui_PR-1922/bundles/org.eclipse.ui.workbench/META-INF/MANIFEST.MF)
11:15:13.409 [WARNING] 1 API problems can't be mapped to the compiler log!

[github-actions]

Test Results

 1 818 files  ±0   1 818 suites  ±0   1h 51m 41s ⏱️ + 1m 9s
 7 711 tests ±0   7 482 ✅ ±0  228 💤 ±0  1 ❌ ±0 
24 294 runs  ±0  23 546 ✅ ±0  747 💤 ±0  1 ❌ ±0 

For more details on these failures, see this check.

Results for commit e53c3c3. ± Comparison against base commit 9f38380.

[iloveeclipse]

OK, API tooling reports an error as expected and it is visible here:

and here

So whatever was in #2430 #1922 is not a "generic" problem of broken API tooling that seem to work, at least at the latest platform state of today.

@HannesWell , @laeubi : FYI