Add audit reports for missing JUnit version ranges across all submodules

[Copilot]

JUnit 6 migration requires proper version ranges on all JUnit bundle and package imports to prevent compatibility issues. This audit identifies all MANIFEST.MF files lacking these constraints.

Reports Generated

• JUNIT_AUDIT_README.md - Quick reference with fix examples
• JUNIT_VERSION_RANGE_AUDIT.md - Complete findings by repository (436 lines)
• JUNIT_VERSION_RANGE_AUDIT.csv - Tracking spreadsheet (119 rows)

Scan Results

Scanned 1,165 MANIFEST.MF files across main repo + 12 submodules:

Repository	Issues
eclipse.jdt.ui	42
eclipse.pde	29
eclipse.platform.releng	15
eclipse.platform.ui	12
eclipse.platform	10
equinox	5
eclipse.jdt.core	4
eclipse.jdt.debug	2

Issue Types

Missing bundle-version on Require-Bundle:

❌ Require-Bundle: org.junit
✅ Require-Bundle: org.junit;bundle-version="[4.13.0,5.0.0)"

Missing version on Import-Package:

❌ Import-Package: org.junit.jupiter.api
✅ Import-Package: org.junit.jupiter.api;version="[5.8.0,6.0.0)"

Each report groups issues by repository to enable tackling them one submodule at a time.

Original prompt

Scan the repository and all its submodule for missing verion ranges on junit bundles and package imports

We have a problem with JUnit 6 migration where manifest have missing import range on packages and bundles

(see for example eclipse-platform#3431

but the git history of the submodules should contain many more examples.

What we need is

• Check this repo and all its submodule for MANIFEST.MF files that still have unrestricted imports
• Make a list grouped by submdule/repository where import ranges are missing so we an tackle the issue one by one

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.