Bump lower bound of google-cloud-bigtable to 2.44

[aIbrahiim]

fixes #30760, fixes #34990

google-cloud-bigtable 2.44 changed DirectRow and PostCommit test_bigtable_write started to fail so the driver uses 2.44 and workers still use 2.42, so pickle loses _pb_mutations

The PR fills _pb_mutations before pickle and before write so old workers can still write the rows

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Assigning reviewers:

R: @damccorm for label python.
R: @igorbernstein2 for label bigtable.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[Amar3tto]

Tested: https://github.com/apache/beam/actions/runs/34204205571

[Abacn]

cc: @mutianf (for Bigtable client breaking change)

Also we should regenerate Python requirement, especially bump this line:

beam/sdks/python/container/py310/base_image_requirements.txt

Line 67 in c4cfdef

google-cloud-bigtable==2.42.0

should fix the issue. cc: @shunping ( regenerate Python requirement then release a new beam-master image)

[shunping]

I didn't know there would be an issue on pickling here. How about we just bump the lower bound of bigtable?

Then we can also simplify the current code to only support bigtable>=2.44

[aIbrahiim]

@Abacn thanks, I can bump bigtable to >=2.44.0 in setup.py and drop the pickle fix

@shunping would you regenerate the Python container requirements and publish a new beam-master image so workers get 2.44 too?

[shunping]

Sure. We can help generate the new beam image.

[aIbrahiim]

Sure. We can help generate the new beam image.

Thanks, I bumped the lower bound and removed the pickle fix

[aIbrahiim]

@shunping also XLang still has the _get_mutation_pbs / _get_mutations from #40029, so should we keep that or drop the old _get_mutations path in this PR now that setup.py requires >=2.44?

[shunping]

LGTM!

@shunping also XLang still has the _get_mutation_pbs / _get_mutations from #40029, so should we keep that or drop the old _get_mutations path in this PR now that setup.py requires >=2.44?

I gave that a second thought, and I think we have to keep the old code path for now so that the internal tests would not be broken.