feat(protocol-designer): allow to track a reported error on Sentry

[koji]

Overview

allow to track a reported error on Sentry

we can do search the uuid on Sentry

errorId:error-uuid

Test Plan and Hands on Testing

Changelog

Review requests

Risk assessment

low

[Copilot]

Pull Request Overview

This PR enhances error tracking in the Protocol Designer by adding the error UUID as a Sentry tag, making it easier to search for specific error reports using the errorId:error-uuid syntax in Sentry's search interface.

Key Changes:

• Modified the Sentry captureException call to include errorId as both an extra field and a tag

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 55.57%. Comparing base (82ec056) to head (5d49a6b).

Additional details and impacted files

@@                    Coverage Diff                     @@
##           chore_release-pd-8.6.3   #20001      +/-   ##
==========================================================
- Coverage                   57.99%   55.57%   -2.43%     
==========================================================
  Files                        3413     3557     +144     
  Lines                      283940   301173   +17233     
  Branches                    39368    40279     +911     
==========================================================
+ Hits                       164671   167372    +2701     
- Misses                     118996   133527   +14531     
- Partials                      273      274       +1     

Flag	Coverage Δ
protocol-designer	18.71% <100.00%> (-0.12%)	⬇️

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

Files with missing lines	Coverage Δ
...gner/src/resources/ProtocolDesignerAppFallback.tsx	84.90% <100.00%> (+1.23%)	⬆️

... and 779 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[SyntaxColoring]

I'm not sure I follow. From this part of the Sentry docs, it sounds like tags are supposed to help with filtering and aggregating error instances together. If every instance of an error is tagged with its own random unique ID, how does that help?

[jerader]

i have the same question as Max 🤔