Suppress deprecation warnings and update deprecated API calls - #7321

Add @SuppressWarnings annotations for deprecated and removal APIs across multiple modules. Update ExtendedFormEditor to use current JFaceResources API methods (destroy/create instead of destroyImage/createImage). Remove deprecated servicefactory parameter from Component annotation in test.

fix gradle-plugin warnings

fix JUnit deprecation warning

Update ArgumentsProvider to match JUnit 5.10+ API
JUnit Jupiter's ArgumentsProvider interface changed to include a ParameterDeclarations parameter in the provideArguments method. Update three test classes that implement custom argument providers to match the new signature.

try to fix maven deprecation warnings

Replace Maven @component with @Inject in Maven plugins

Update all Maven plugin mojos to use standard JSR-330 @Inject annotation instead of Maven-specific @component annotation. This removes the warnings and uses the dependency injection approach to use standard Java conventions supported by Maven 3.9+.
See https://maven.apache.org/maven-jsr330.html#how-to-use-jsr-330-in-plugins

Clean up resource management and remove unused code

Wrap P2Indexer instantiations in try-with-resources for proper cleanup, remove unused imports

Changes:
- Wrap P2Indexer objects in try-with-resources blocks to ensure cleanup
- Move AssertJ SoftAssertions imports to group with test configuration
- Remove unused imports (java.util.Map, org.apache.maven.project.MavenProjectHelper)
- Remove unused FEATURE_PATTERN constant from R5LabelFormatter
- Fix minor whitespace inconsistencies

Signed-off-by: Christoph Rueger <[email protected]>