Remove requirement of inlined o.e.jdt.launching.macosx fragment

[HannesWell]

Part of

• Inline o.e.jdt.launching.macosx into jdt.launching eclipse-jdt/eclipse.jdt.debug#855

[vogella]

I think that is what currently fails the aggregator build, eclipse-platform/eclipse.platform.releng.aggregator#3888

Thanks!

[HannesWell]

I think that is what currently fails the aggregator build, eclipse-platform/eclipse.platform.releng.aggregator#3888

Yes it is. But since there is some chicken-egg problem when resolving the removal/inlining of the previous needed fragment there is no (trivial) perfect way to do it and this will probably fail some tests until the inlining has passed an I-build.
But since verification builds of multiple repositories will fail with this applied I decided to do it close to the I-build start.
The aggregator verification build failing over the day was IMO the smaller collateral damage.

[github-actions]

Test Results

    54 files  ±0      54 suites  ±0   50m 57s ⏱️ - 3m 6s
 4 671 tests ±0   4 618 ✅  - 31   22 💤 ±0  30 ❌ +30  1 🔥 +1 
11 907 runs  ±0  11 723 ✅  - 31  153 💤 ±0  30 ❌ +30  1 🔥 +1 

For more details on these failures and errors, see this check.

Results for commit 0648b71. ± Comparison against base commit abad270.

[HannesWell]

Test failures on Mac are expected because the inlined code of the fragment is only available in the new target bundle after tonight's I-build.

[vogella]

Thanks for the update, yes a aggregator failing for a day or so is fine IMHO for such a nice improvement. Thanks for working on this