refactor: dedupe sentry trace

[gambinish]

Explanation

Gaps to close (likely in the sibling client PRs, not core)

• late_success/late_error is the taxonomy used, rather than timeout so some dashboards may need to be updated.
• docs/perps/perps-sentry-reference.md (mobile) still needs updating to describe the new controller-owned trace semantics and the removal of the toast trace.
• removing usePerpsMeasurement({ traceName: PerpsOrderSubmissionToast }) from usePerpsOrderExecution.ts, deleting the PerpsOrderSubmissionToast TraceName from app/util/trace.ts, and the mobile-side Promise.race.
• the core tests cover the meaningful equivalents (fast/late success, fast/late error). The literal "timeout" and "navigation-away" cases don't apply in core; that's fine, but the epic's mobile PR should still cover navigation-away at the UI layer if any UI tracing remains.

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Changes real order-submission observability and trace payloads for a core trading path; behavior intentionally avoids client-side cancellation, but consumers may rely on new reason values.

Overview
Adds a 60s observational threshold (PlaceOrderTimeoutMs) on TradingService.placeOrder: when the provider round-trip runs long, the code emits a warning breadcrumb and debug log but does not cancel the in-flight placeOrder (avoids false failures if HyperLiquid still accepts the order).

Perps Place Order trace end data now includes optional reason: late_success / late_error when the outcome arrives after the threshold, or error otherwise; successful fast paths omit reason.

Removes the unused Perps Order Submission Toast entry from PerpsTraceName. Adds focused unit tests for threshold timing, trace reasons, and timer cleanup.

^{Reviewed by Cursor Bugbot for commit a4f810d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a4f810d. Configure here.}

[cursor]

Late error mislabels post-provider failures

Medium Severity

The catch path sets trace reason to late_error whenever didExceedOrderSubmissionThreshold is true, including when provider.placeOrder already finished successfully and a later step (e.g. #handleOrderSuccess or #trackOrderResult) throws. That labels a slow-but-successful submission as a late provider error in Sentry.

 

^{Reviewed by Cursor Bugbot for commit a4f810d. Configure here.}

[aganglada]

legit?