Shared suites for Maven/Gradle Tests

[sharma1208]

Builds on #606
Fixes #607

Summary

After the POM refactor (#606), Maven and Gradle test files were nearly identical except for build-tool-specific data (project paths, parameter formats, report locations). This PR collapses each test pair into shared parameterized suites, eliminating ~50% of test code duplication.

Changes

Created 3 Shared Test Suites (src/test/shared/)

1. restSnippetSuite.ts

   • Parameterized REST snippet and diagnostic tests
   • Config: { buildTool, getProjectPath }
   • Eliminates ~200 lines of duplication per build tool

2. hoverTestSuite.ts

   • Parameterized hover tests
   • Config: { buildTool, getProjectPath, hoverTestCases }
   • Handles build-tool-specific line numbers (server.xml differences)
   • Eliminates ~150 lines of duplication per build tool

3. devModeTestSuite.ts

   • 6 shared DevMode tests: Find sidebar, Show items, Start, Start with Docker, Run tests, Attach debugger
   • Config: { buildTool, getProjectPath, projectConstant, testRunString }
   • Maven/Gradle-specific tests remain in separate describe blocks

Refactored Entry Files

Each Maven/Gradle entry file now:

• Calls the shared suite with build-tool-specific config (~4 lines)
• Keeps build-tool-specific tests in separate describe blocks (where needed)

[sharma1208]

force rebase due to changes on POM refactoring moving methods to editorUtils.ts #606

[mattbsox]

Looks good, but I think we'll need to refactor the Gradle 9 test too.