fix(bigtable): Use retry policy on streams with failing mutations

[dbolduc]

Fixes #7479

Streams with an OK status, but failing mutations count towards the retry policy.

While the 4 tests don't look like each other, they are consistent with the other tests in their fixtures, namely the TooManyFailures or *Exhausted tests.

---

This change is 

[google-cloud-cpp-bot]

Google Cloud Build Logs
For commit: ecd1ca6a1faa56b752fb63137e5caa916aedf786

• Public Access Build Logs
• Cloud Build Console (requires auth)
• Kokoro Logs (requires auth)

ℹ️ NOTE: Kokoro logs are linked from "Details" below.

[codecov]

Codecov Report

Merging #9706 (ecd1ca6) into main (1abf599) will increase coverage by 0.00%.
The diff coverage is 96.12%.

@@           Coverage Diff            @@
##             main    #9706    +/-   ##
========================================
  Coverage   93.89%   93.89%            
========================================
  Files        1496     1496            
  Lines      139384   139503   +119     
========================================
+ Hits       130878   130993   +115     
- Misses       8506     8510     +4     

Impacted Files	Coverage Δ
google/cloud/bigtable/table.h	98.54% <ø> (ø)
...oud/bigtable/internal/data_connection_impl_test.cc	96.66% <92.59%> (-0.11%)	⬇️
google/cloud/bigtable/table_bulk_apply_test.cc	98.25% <95.45%> (-0.30%)	⬇️
.../bigtable/internal/legacy_async_bulk_apply_test.cc	98.67% <97.05%> (-0.21%)	⬇️
...e/cloud/bigtable/internal/async_bulk_apply_test.cc	97.03% <97.43%> (+0.04%)	⬆️
google/cloud/bigtable/internal/async_bulk_apply.cc	100.00% <100.00%> (ø)
...le/cloud/bigtable/internal/data_connection_impl.cc	98.80% <100.00%> (ø)
...cloud/bigtable/internal/legacy_async_bulk_apply.cc	100.00% <100.00%> (ø)
google/cloud/bigtable/table.cc	99.42% <100.00%> (-0.01%)	⬇️
...e/cloud/pubsublite/internal/alarm_registry_impl.cc	97.05% <0.00%> (-2.95%)	⬇️
... and 5 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.