fix: Correct AsyncTransaction Return Types

[TimPansino]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #750

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[TimPansino]

Completely unrelated to this PR, it looks like your repo doesn't have unit (3.11) set as a required check. Might want to change that setting.

[daniel-sanche]

So it looks like there's a mismatch between what is returned and what is declared in the type hints. I agree with this fix to align with the type hints in principle, but I am worried that it could break existing users who are used to the "wrong" return value

You mention that you see errors whether you treat the result as a coroutine or an async generator. Is there really no way to access the generator?

Right now, I'm thinking this would make sense to address in a future breaking change, along with other type fixes needed as part of #773. But we can probably get this in sooner if it really is completely broken as-is

[parthea]

Converting to draft as there has been no recent activity