Prepare 4.38 development

[eclipse-releng-bot]

Prepare development of Eclipse 4.38.
This complements:

• Prepare 4.38 development eclipse-platform/eclipse.platform.releng.aggregator#3271

[github-actions]

Test Results

  256 files   -   128    256 suites   - 128   32m 59s ⏱️ - 9m 48s
1 899 tests  -     6  1 896 ✅  -     6  3 💤 ±0  0 ❌ ±0 
4 480 runs   - 2 235  4 474 ✅  - 2 232  6 💤  - 3  0 ❌ ±0 

Results for commit a286666. ± Comparison against base commit 0814abd.

This pull request removes 6 tests.

AutomatedTests org.eclipse.equinox.p2.tests.touchpoint.natives.AllTests org.eclipse.equinox.p2.tests.touchpoint.natives.CheckAndPromptNativePackageWindowsRegistryTest ‑ execute_IntAttribute
AutomatedTests org.eclipse.equinox.p2.tests.touchpoint.natives.AllTests org.eclipse.equinox.p2.tests.touchpoint.natives.CheckAndPromptNativePackageWindowsRegistryTest ‑ execute_IntAttribute_DifferentLiteralValue
AutomatedTests org.eclipse.equinox.p2.tests.touchpoint.natives.AllTests org.eclipse.equinox.p2.tests.touchpoint.natives.CheckAndPromptNativePackageWindowsRegistryTest ‑ execute_KeyExistence
AutomatedTests org.eclipse.equinox.p2.tests.touchpoint.natives.AllTests org.eclipse.equinox.p2.tests.touchpoint.natives.CheckAndPromptNativePackageWindowsRegistryTest ‑ execute_KeyExistence_DifferentKeys
AutomatedTests org.eclipse.equinox.p2.tests.touchpoint.natives.AllTests org.eclipse.equinox.p2.tests.touchpoint.natives.CheckAndPromptNativePackageWindowsRegistryTest ‑ execute_StringAttribute
AutomatedTests org.eclipse.equinox.p2.tests.touchpoint.natives.AllTests org.eclipse.equinox.p2.tests.touchpoint.natives.CheckAndPromptNativePackageWindowsRegistryTest ‑ execute_StringAttribute_DifferentValues

♻️ This comment has been updated with latest results.

[HannesWell]

The automated change looks as intended.

But the new API-tools warnings are not optimal. Does anybody have an idea why thy pop-up now?

[HannesWell]

But the new API-tools warnings are not optimal. Does anybody have an idea why thy pop-up now?

Looking at the latest master builds, these warnings just vanished (for unknown reasons) in the last build and where already present before. So I'll ignore these warnings for now and leave it as a task for later to suppress/filter or fix them.