fix(storage): consume server responses before finishing stream in AsyncWriter Close/Finalize

[kalragauri]

This PR fixes an issue where calling AsyncWriter::Close() or Finalize() hangs indefinitely when the GCS service returns intermediate response messages before closing the stream.

Under the hood, Close() sends a kFlushAndClose request, which prompts GCS to respond. Previously, AsyncWriterConnectionImpl called Finish() on the underlying gRPC stream immediately after writing without consuming any remaining server responses. This unread data on the stream caused Finish() to block waiting for response consumption, leading to a deadlock.

[gemini-code-assist]

Code Review

This pull request refactors OnClose and OnFinalUpload in AsyncWriterConnectionImpl to use a recursive ConsumeLoop that reads and processes all intermediate server responses before finalizing the upload, preventing hangs when multiple responses are sent before EOF. Corresponding unit tests are updated and a new test is added to verify this behavior. The review feedback correctly identifies compilation errors in both refactored methods where the undefined variable self is referenced inside lambdas capturing [this], and provides code suggestions to resolve these issues by calling Finish() directly.