[Feature]: Send version, platflorm etc automagically to feedback

[LinkeD365]

Fixes #528

Co-authored-by: Copilot copilot@github.com

Please fill in this template.

• Use a meaningful title for the pull request.
• Follow the guidelines from the CONTRIBUTING.md.
• Mention the bug or the feature number the PR will be targeting.
• Test the change in your own code. (Compile and run)
• Resolve all GH Copilot comments.

[github-actions]

Bundle Size Report 📦

Bundle	Size
Main Process	958.12 KB
Renderer JS	545.09 KB
Renderer CSS	96.19 KB
Total	1.56 MB

Bundle Analysis Reports

The detailed bundle analysis reports are available in the workflow artifacts:

• 📊 Main Process: stats-main.html
• 📊 Renderer Process: stats-renderer.html

Download the artifacts from the workflow run to view interactive visualizations.

---

Bundle size tracking is now active! This helps prevent bundle bloat.

[Copilot]

Pull request overview

Updates the Help → “ToolBox Feedback” menu action to open a pre-filled GitHub bug report, automatically including basic environment diagnostics (app/runtime/platform) and active tool metadata to speed up issue triage (Fixes #528).

Changes:

• Replace the “ToolBox Feedback” external link with a generated /issues/new URL using the bug-report issue form template.
• Add buildToolBoxFeedbackUrl() to prefill version/log fields with environment details and active tool info.
• Minor cleanup: remove an outdated comment in the Supabase connectivity check.

[LinkeD365]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Applied both review suggestions in commit 01af851:

1. Fallback URL — changed from the generic /issues list to /issues/new?template=issue-form-bug.yml so users always land on the bug-report form, even when buildToolBoxFeedbackUrl() throws.

2. Instance ID vs Tool ID — added a separate Active Tool Instance ID line to the environment summary so the raw instance ID and the parsed tool ID are clearly distinct fields. Also changed the fallback for an unparseable instance ID from re-using the instance ID (which could be mistaken for a tool ID) to "unknown".