Add tests for GatherUnusedDependenciesOperation

[vogella]

This commit adds a new test class
GatherUnusedDependenciesOperationTest
to verify the behavior of GatherUnusedDependenciesOperation. It includes tests for:

• Identifying unused dependencies.
• Ensuring used dependencies are not reported.
• Handling of mandatory dependencies that are also re-exported by optional dependencies.

The new test is registered in AllPDETests.

If the ignored test is enabled you also have an example for #2115

[github-actions]

Test Results

  330 files   -   441    330 suites   - 441   40m 0s ⏱️ - 15m 58s
  986 tests  - 2 662    955 ✅  - 2 639  30 💤  - 24  1 ❌ +1 
2 892 runs   - 7 986  2 798 ✅  - 7 917  91 💤  - 72  3 ❌ +3 

For more details on these failures, see this check.

Results for commit 79d8945. ± Comparison against base commit abc3cc7.

This pull request removes 2665 and adds 3 tests. Note that renamed tests count towards both.

JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[JUnit4 (JUnitPlatform) Fragment]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[JUnit4 (JUnitPlatform)]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[JUnit4 Fragment]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[JUnit4]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[JUnit5 Fragment]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[JUnit5]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[JUnit6 Fragment]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[JUnit6]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[Java 11 bundle with module limit]
JUnitRuntimeTests org.eclipse.pde.junit.runtime.tests.JUnitExecutionTest ‑ executeMethod[Using a 'test' source folder]
…

AllPDETests GatherUnusedDependenciesOperationTest ‑ testFindUnusedDependency
AllPDETests GatherUnusedDependenciesOperationTest ‑ testMinimizeRemovesMandatoryIfOptionalReexports
AllPDETests GatherUnusedDependenciesOperationTest ‑ testUsedDependencyNotReported

[laeubi]

I would strongly recommend not creating test classes / bundles "inline" as it bloats the test (what makes it hard to read) and is harder to analyze (e.g. no real project structure to look at in the IDE only temporary java/class files).

It would be better to have a set of bundles that is then used in the test and can be imported for example in a workspace to see the problem in action.

[laeubi]

Why?