chore: test aborted transactions with tags

[olavloite]

Add tests that verify that the transaction tag is set both for the original attempt and any retries of a read/write transaction.

When using multiplexed sessions, the BeginTransaction RPC should also include a transaction tag.

[gemini-code-assist]

Summary of Changes

Hello @olavloite, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces comprehensive testing for transaction tags, specifically focusing on their persistence and correct application during aborted and retried read/write transactions. The changes aim to validate that transaction tags are consistently propagated across various transaction-related requests, thereby improving the robustness and observability of transaction management.

Highlights

• Transaction Tag Verification: New tests have been added to ensure that transaction tags are correctly applied to both initial and retried read/write transactions, validating their persistence across transaction lifecycle events.
• Multiplexed Sessions: The pull request highlights that the BeginTransaction RPC should include transaction tags when multiplexed sessions are in use, indicating an area for future enhancement or verification.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request introduces new tests to verify that transaction tags are correctly applied to both original and retried attempts of read/write transactions, especially when transactions are aborted. This is a valuable addition for ensuring the robustness and correctness of transaction handling with tags. The changes also include making AbortNextStatement public in the mock server, which is appropriate for testing purposes.