fix(storage): do not retry permanent errors in async writer resume

[v-pratap]

Summary

This PR fixes a bug in Storage async writer connections (AsyncWriterConnectionResumed and AsyncWriterConnectionBuffered) where permanent errors (such as FAILED_PRECONDITION) were being retried during streaming write operations.

Cause

Previously, when a stream error occurred during Write, Flush, Close, Finalize, or Query, Resume(Status const& s) was called unconditionally without checking if s was a permanent failure. For appendable uploads (BidiWriteObject), issuing a new BidiWriteObject RPC on Resume() requested writer exclusivity from the server, causing concurrent writers to continuously steal exclusivity back and forth from each other in an infinite loop upon receiving FAILED_PRECONDITION.

Fix

• Updated Resume(Status const& s) in writer_connection_resumed.cc and writer_connection_buffered.cc to check if s is a permanent failure (via AsyncRetryPolicy / AsyncStatusTraits) before attempting Resume().
• If s is a permanent failure (such as FAILED_PRECONDITION), the connection immediately terminates with status s via SetError(...) without opening a new stream.
• Added unit tests WriteConnectionResumed.PermanentErrorNoResume and WriteConnectionBuffered.PermanentErrorNoResume to verify that permanent errors on active streams do not trigger resume attempts.

[gemini-code-assist]

Code Review

This pull request introduces OpenTelemetry tracing and metrics support to the asynchronous OpenObject class, adding a new OpenObjectTelemetry helper class and corresponding unit tests. It also updates the buffered and resumed writer connections to prevent resume attempts on permanent failures. The review feedback correctly identifies a build issue where GOOGLE_CLOUD_CPP_HAVE_OPENTELEMETRY is unconditionally defined as PUBLIC in CMake, which would break builds when OpenTelemetry is disabled. Additionally, the reviewer suggests correcting the header inclusion in open_object.cc to include the trace provider instead of the metrics provider, as the file only retrieves the current span and does not record metrics directly.

[codecov]

Codecov Report

❌ Patch coverage is 96.26168% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 92.23%. Comparing base (154f9ef) to head (4af6792).

Files with missing lines	Patch %	Lines
...e/internal/async/writer_connection_resumed_test.cc	92.85%	4 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #16340   +/-   ##
=======================================
  Coverage   92.23%   92.23%           
=======================================
  Files        2227     2227           
  Lines      209283   209378   +95     
=======================================
+ Hits       193026   193125   +99     
+ Misses      16257    16253    -4     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.