chore: migrate Trace Viewer tests to use real Trace viewer

[mxschmitt]

Fixes #1829

[Copilot]

Pull Request Overview

This PR migrates Trace Viewer tests from a JSON-based approach to using the actual Trace Viewer web application for validation. The change improves test coverage by testing the real UI components instead of just parsing trace files.

• Replaced JSON parsing and verification of trace events with actual Trace Viewer UI interactions
• Added a new TraceViewerPage helper class to encapsulate Trace Viewer UI operations
• Enhanced the test server to serve static files from the filesystem to support hosting the Trace Viewer

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
TestTracing.java	Migrated all trace verification logic from JSON parsing to Trace Viewer UI testing, added TraceViewerPage helper class
Server.java	Added static file serving capability to support hosting Trace Viewer from filesystem

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[mxschmitt]

underneath we do something similar but via getResourceAsStream which got introduced here - do you remember why?

[yury-s]

This is the standard way to read resources in a maven package (they move from the source into the test package artifact). I'd keep using it with the custom base dir too, can we do that?

[mxschmitt]

I think there is no way of accessing the trace-viewer html source code via the tests/resource directory so I introduced another resourceLoader concept - are you fine with that?

[yury-s]

Yes. I'd pass the resource provide in server the constructor.

[yury-s]

This is the standard way to read resources in a maven package (they move from the source into the test package artifact). I'd keep using it with the custom base dir too, can we do that?

[yury-s]

Looks good, but please revert changes in DriverJar.java