Remove <2.0.0 limit on google-cloud-bigtable

[r-richmond]

related: #27292
related: #26922

What this does

• Removes <2.0.0 limit on google-cloud-bigtable and corresponding protobuf limit
  • google-cloud-bigtable no longer requires <= 3.2.0 on protobuf

Why

• python 3.11 support
• the corresponding protobuf limit restricted multiple other packages from later versions
  • Of interest to me it limited google-cloud-aiplatform to 1.13.1
  • which limited google-cloud-bigquery to >=1.15.0,<3.0.0dev
• Only 1 non-significant breaking change in google-cloud-bigtable 2.0+
  • Microgenerator changes which removes support for python <= 3.5
  • No other breaking changes in release notes

Update

• Updated pr to account for Enum import path moving slightly and type changes

[uranusjr]

ImportError: cannot import name 'enums' from 'google.cloud.bigtable_admin_v2'

Looks like there are incompatibilities.

[r-richmond]

Looks like there are incompatibilities.

Yep, looks like the release notes weren't as truthful this time.. I'll see if I can I fumble my way through this bit later today. (Little difficult on my end since I don't actually use big table just big query but 🤷 )

[r-richmond]

@uranusjr think I got everything. Last test failed due to 2 hour queue timeout.

[potiuk]

@uranusjr think I got everything. Last test failed due to 2 hour queue timeout.

Yeah - we had some "blocked" build queue - I unblocked it now. Rebasing to re-run.

[r-richmond]

Latest failure looks like another pipeline issue unrelated to this change

/home/runner/work/_temp/5e427642-8610-4b5e-8e04-24f61c20032d.sh: line 1: 4290 Killed breeze testing tests --run-in-parallel
371

[r-richmond]

This hit the same error that my local run of find newer dependencies did. Not sure what to do from here..

[uranusjr]

The error is from a bug in our CI setup code. I opened a PR (linked above) to fix it.

[potiuk]

Nice. That one brings us much closer to Python 3.11 support.

[potiuk]

The error is from a bug in our CI setup code. I opened a PR (linked above) to fix it.

Thanks @uranusjr ! That was a bummer :)