fix: improve ignore path matching to prevent false positives

[viogustian]

closes #116

Problem

The current implementation uses a raw .StartsWith() check for ignored paths. This causes unrelated endpoints that happen to share the same prefix to be incorrectly ignored when a base path is configured.

Solution

Updated IsIgnoredPath in DebugProbeMiddleware to use boundary-aware matching. The logic now strictly checks for an exact match (path.Equals) or a valid child path by appending a trailing slash (path.StartsWith(ignorePath.TrimEnd('/') + "/")).

Testing

• Reproduced the bug where /healthcare was incorrectly dropped when /health was ignored.
• Added a unit test (Similar_paths_are_not_skipped) in MiddlewareExecutionFlowTests to verify similar but distinct paths are recorded correctly.
• All tests pass successfully.

[georgidhristov]

Tested locally with configured ignore paths.

Verified that exact matches and child paths are ignored correctly, while similar paths such as /healthcare continue to be captured.

Thanks for the contribution. I really appreciate your help improving DebugProbe and taking the time to work on these issues.

Feel free to pick up more issues in the future if something looks interesting to you. Contributions are always welcome.