…t redirects (#16073)

* fix(storage): Handle request transformation correctly after BidiWriteObject redirects

This commit addresses an issue where BidiWriteObject operations, particularly in cross-region redirect scenarios, would fail with a NOT_FOUND error. The root cause was that bucket information was not propagated in the request headers after the client received a redirect error from the service.

…16078)

…dentials (#16080)

…loads (#16083)

When a stream breaks, the connection enters a resume state. A key step in OnResume is to create a new underlying connection. This new connection is initialized to start writing data from the persisted size reported by the GCS backend.

The existing logic did not work as expected in some cases because it used relative decrements that became invalid after buffer truncation. This could happen if the size of payload persisted by the server did not match the size sent by the client.

This change introduces an is_resume flag to the OnQuery method. When OnQuery is called as part of the Resume() flow (i.e., after a new underlying connection is established), write_offset_ is now explicitly set to 0. This ensures that the WriteLoop correctly starts sending from the beginning of the truncated resend_buffer_ on the resumed stream.