[Enhancement] Show Semantic Dedup Post processor result in Sygra Studio

[psriramsnc]

✨ Summary

This PR adds first-class support for post-processor artifacts in execution outputs, including Semantic Deduplication artifacts, with both backend discovery APIs and rich frontend visualization. Users can now browse, inspect, copy paths, and download post-processor outputs directly from the SyGra Studio, making debugging and analysis significantly easier.

🚀 Explain the features implemented:

• Backend API for post-processor artifacts

  • Added /api/executions/{execution_id}/artifacts/post-processors to discover post-processor output files for an execution.
  • Automatically detects and groups artifacts, including Semantic Deduplication reports and final outputs.
  • Filters out main execution output files and returns relative paths when possible.

• Semantic Deduplication SyGra Studio support 🧠

  • Dedicated UI section for Semantic Deduplication artifacts.
  • Special handling for deduplication reports to render duplicate entries in a tabular view.
  • Clear labeling and grouping for report vs final output files.

• Generic post-processor artifact rendering 📦

  • Groups artifacts by post-processor key with expandable sections.
  • Supports table, JSON, and raw views depending on artifact structure.
  • One-click download for artifact JSON files.

• Improved UX & state management 🎨

  • Lazy loading of artifacts only when the Output tab is active.
  • Loading indicators, empty-state messaging, and copy-to-clipboard for artifact paths.
  • State resets automatically when execution context changes.

⚡ Performance impact (if any):

• Minimal impact
  • Artifacts are fetched lazily and only once per execution.
  • Large datasets are capped in the UI to avoid performance issues.

🧪 How to Test the feature

1. Navigate to an execution details page and open the Output tab.
2. Run or open an execution that has post-processors enabled (e.g. Semantic Dedup).
3. Expand Semantic Deduplication or other post-processor sections.
4. Verify:
   • Artifacts appear with correct labels and paths.
   • Data renders correctly in table/JSON views.
   • Download and copy-path actions work.
   • Empty state appears when no artifacts are present.

🖼️ Screenshots (if applicable)

✅ Checklist

• Lint fixes and unit testing done
• End to end task testing
• Documentation updated

📝 Notes

• Semantic Dedup artifacts are detected via filename conventions; metadata-based discovery can be added later.
• This change enables future post-processors without requiring backend changes.