fix(api): downgrade client cancellation from error to warning

[dobrac]

Summary

• Detect context.Canceled in the logging middleware and OTEL tracing middleware to distinguish client disconnects from real server errors
• Logging middleware now logs canceled requests at Warn instead of Error, even when the HTTP status is 5xx
• OTEL tracing middleware sets a client.canceled=true span attribute instead of marking the span as an error status

---

Note

Medium Risk
Small change but it alters how 5xx requests are classified in logs and OpenTelemetry spans, which can impact alerting and error-rate dashboards if cancellation detection is wrong.

Overview
Adjusts request observability to distinguish client disconnects from server failures: the logging middleware no longer emits 5xx responses as Error when the request context is context.Canceled, and the OTEL tracing middleware avoids setting an error span status for canceled requests, instead tagging spans with client.canceled=true.

^{Written by Cursor Bugbot for commit 3da0327. This will update automatically on new commits. 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, enable autofix in the Cursor dashboard.}