feat: Easy session failure reporting

[ki3ani]

Summary

Implements #3244 - adds "Report a Failure" button with automated system info collection and GitHub Issues integration.

Users can now report failures directly within the app instead of manually navigating to GitHub. The modal automatically collects system information and submits reports with
proper error handling and fallback logging.

Screenshots

Before: Settings Help & Feedback Section

After: New "Report a Failure" Button Added

Report Failure Modal - System Info Auto-Collection

Success State After Submission

Implementation Details

• ReportFailureModal component with form validation and automatic system info collection
• Backend API endpoint /report-failure with GitHub Issues integration and fallback logging
• Automatic data collection: Goose version, platform, architecture, extension count, provider type, recent errors
• GitHub integration creates properly formatted issues matching the bug report template
• Fallback logging ensures reports are captured even when GitHub API is unavailable
• Proper error handling with user feedback for all failure scenarios

Technical Changes

Frontend (ui/desktop/)

• Added ReportFailureModal.tsx with system info collection logic
• Enhanced AppSettingsSection.tsx to include the new "Report a Failure" button
• Extended preload.ts to expose process.arch for architecture detection

Backend (crates/goose-server/)

• Added /report-failure endpoint in feedback.rs
• GitHub Issues API integration with proper authentication
• Structured logging for manual processing when API unavailable
• Bug report template formatting matching existing GitHub templates

Test Plan

• Modal opens and automatically collects system information
• Form validation prevents empty submissions
• API endpoint receives and processes failure reports correctly
• GitHub issue format matches existing bug report template structure
• Fallback logging works when GitHub token not available
• Success/error states provide appropriate user feedback
• System info collection works across different platforms

Notes

• Requires GITHUB_TOKEN environment variable for GitHub Issues integration
• Falls back to local logging when GitHub API unavailable
• Architecture detection now properly exposed through Electron API
• Version detection includes fallback for development builds

[jamadeo]

Thanks @ki3ani this is a good feature. However I don't think we should dependon a github token set in goosed -- rather, you can do this more simply by opening the system web browser at something like

https://github.com/block/goose/issues/new?title=YOUR_TITLE&body=YOUR_BODY&labels=LABEL1,LABEL2&milestone=MILESTONE_NAME&assignees=ASSIGNEE1,ASSIGNEE2&template=TEMPLATE_NAME

[ki3ani]

Thanks @ki3ani this is a good feature. However I don't think we should dependon a github token set in goosed -- rather, you can do this more simply by opening the system web browser at something like

https://github.com/block/goose/issues/new?title=YOUR_TITLE&body=YOUR_BODY&labels=LABEL1,LABEL2&milestone=MILESTONE_NAME&assignees=ASSIGNEE1,ASSIGNEE2&template=TEMPLATE_NAME

That was well noted @jamadeo, ive refactored to open pre-filled GitHub URL in browser instead.