In-app reporting for failed runs and workflow errors

[LuD1161]

Description:
When a workflow fails (e.g., Subfinder node error: Failed to start Docker container: spawn docker ENOENT), users should have an easy way to report the issue or ask for help directly from the interface.

Instead of silently failing, the platform should surface a “Report Issue” or “Give Feedback” button near the error logs panel. This allows users to attach screenshots, logs, and comments that help us debug or improve the workflow reliability.

User Story:

As a user, when a workflow fails, I want to quickly report the error (with logs and screenshots) without leaving the app, so that the team can investigate or assist me.

Acceptance Criteria:

• Add a "Report Issue" button in the run details/logs view for failed workflows.

• Clicking the button opens a feedback modal where users can:

  • Add a short message or description.
  • Attach a screenshot (auto-capture the workflow canvas + logs if possible).
  • Auto-populate run metadata (workflow name, run ID, component name, error code).

• Submit feedback to a backend endpoint (or GitHub issue via API) for triage.

• Optional: Allow tagging feedback as bug, question, or suggestion.

• Feedback entries appear in the admin dashboard for review.

Dependencies:

• Relies on error logging and workflow run context.
• Should integrate cleanly with current run execution panel (like in the screenshot).

Example:
In the Subfinder Workflow run, the system failed with spawn docker ENOENT. The user clicks “Report Issue”, attaches the error log, and sends it for triage.