fix: improve 404 error handling to show all relevant parameters

[dcramer]

Instead of trying to guess which resource caused a 404, now we list all path parameters that were used in the API call. This provides clearer error messages that help users identify which parameter might be incorrect.

Example error message:

Resource not found. Please verify these parameters are correct:
  - organizationSlug: 'my-org'
  - issueId: 'PROJ-123'

Changes:

• Simplified error handling to remove operation tracking
• Tools now only pass path parameters that could cause 404s
• Error messages list all relevant parameters for better debugging

Fixes MCP-SERVER-EA1, MCP-SERVER-E9B

🤖 Generated with Claude Code

[codecov]

Codecov Report

Attention: Patch coverage is 98.50746% with 1 line in your changes missing coverage. Please review.

Project coverage is 62.65%. Comparing base (56aff50) to head (b3ee93c).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
packages/mcp-server/src/tools/find-issues.ts	93.75%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #372      +/-   ##
==========================================
+ Coverage   62.46%   62.65%   +0.19%     
==========================================
  Files          77       77              
  Lines        6844     6855      +11     
  Branches      613      613              
==========================================
+ Hits         4275     4295      +20     
+ Misses       2569     2560       -9     

Flag	Coverage Δ
unittests	62.65% <98.50%> (+0.19%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.