[Bug]: adapt to protobuf versioning

[cdeepali]

What happened?

protubuf has adopted a new versioning scheme announced at https://protobuf.dev/news/2022-05-06/#versioning.

As taken from protocolbuffers/protobuf#12062 (comment):

- C++ protobuf releases version numbered {major}.{minor}
- Python protobuf adds 4. prefix to the versions (so git tag v21.12 becomes [4.21.12](https://pypi.org/project/protobuf/4.21.12/) on pypi).
- Java add 3. prefix to the versions (hence git tag v21.12 becomes [3.21.12](https://mvnrepository.com/artifact/com.google.protobuf/protobuf-java/3.21.12).

So looks like there is a need to allow protobuf v4 at https://github.com/apache/beam/blob/v2.43.0/sdks/python/setup.py#L191

Issue Priority

Priority: 3 (minor)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[AnandInguva]

Protobuf was recently updated to 4.x.x at #24599. That change will be included in Beam 2.47.0.

beam/sdks/python/setup.py

Line 251 in 57ac318

'protobuf>=4.21.1,<4.23.0',

[cdeepali]

Thanks @AnandInguva.