feat: enable write retry and nack pending writes on reconnect

[alvarowolfx]

This PR fix an issue that can happen when an error is returned by the service side and we trigger a reconnect, in some cases where a in-flight/pending write is still waiting for response can be left without any ack/nack.

Towards internal b/329875851

[alvarowolfx]

Summary of integration/e2e tests added on this PR:

Test Group: Flaky Scenarios

Test SubGroup: should manage to send data in sequence scenario

• Tries to send 50 AppendRows requests with 10 rows each.
• Requests are sent in sequence - wait for response for current one to send the next.
• Uses PENDING Stream with offset

• Validate that 500 rows are inserted by calling finalize on the stream and checking rowCount.

  Test Name: every 10 request drops the connection

  • Uses reconnect_on_close table ID, which makes connection to be closed after 10 requests

  Test Name: opening the connection can fail more frequently

  • After every successful Append, we close the connection.
  • Uses initial_connect_failure table ID, which makes opening a connection fail 60% of the time.

Test SubGroup: should manage to send data in parallel.

• Tries to send 50 AppendRows requests with 10 rows each.
• Requests are sent all at once asynchronously and we await for all to finish.
• Uses PENDING Stream with offset

• Validate that 500 rows are inserted by calling finalize on the stream and checking rowCount.

  Test Name: every 10 request drops the connection:

  • Uses reconnect_on_close table ID, which makes connection to be closed after 10 requests.

  Test Name: every 10 request there is a quota error:

  • Simulates the service side throwing in stream response error.
  • Throws internal error + grpc status INTERNAL every 10 requests.