Fix frontend finding type mismatch with backend scan response

[aditya-sharma-devs]

Summary

This PR fixes the mismatch between the frontend BackendFinding type and the actual backend Finding model returned by the scan APIs.

Changes Made

• Updated BackendFinding to match the backend response structure.

• Replaced deprecated top-level fields (file, line, tool) with:

  • location.path
  • location.start_line
  • metadata.engine

• Updated the finding mapper to correctly transform backend responses into the UI Finding model.

• Added safe fallbacks to prevent undefined values during rendering.

Testing

• Successfully ran npm run build after the changes.
• Verified that findings continue to map correctly to the UI model.

Fixes #50

[ionfwsrijan]

@aditya-sharma-devs The core implementation is good but i found a couples of flaws in it.

1. confidence is declared twice in BackendFinding
2. reachability?: unknown and features?: unknown are typed as unknown with no structure
3. lineNumber: f.location?.start_line ?? 0 — fallback of 0 is semantically wrong
4. tool: (f.metadata?.engine as Finding["tool"]) ?? "semgrep" which is an unsafe cast

[ionfwsrijan]

@aditya-sharma-devs Join our dc server to connect with fellow contributors and mentors. We'll help you out.

https://discord.gg/FcXuyw2Rs

[aditya-sharma-devs]

Thanks for the review! I'll work through these issues and update the PR with the suggested fixes.