Relax protobuf upper bound for protobuf 6/7 compatibility

Hi, thanks for maintaining aliyun-log-python-sdk.

The latest release 0.9.46 still declares this protobuf dependency range:

protobuf>=3.20.3,<6.0.0

This upper bound prevents projects that use newer protobuf-based libraries from resolving dependencies in the same Python environment. For example, applications that use ConnectRPC / generated protobuf clients may need to integrate with protobuf 6+ compatible packages, but aliyun-log-python-sdk forces the environment to stay on protobuf 5.x.

Would you consider testing aliyun-log-python-sdk with protobuf 6/7 and relaxing the upper bound if compatible? For example:

protobuf>=3.20.3,<8.0.0

or another validated compatible range.

Current workaround on our side is to keep runtime protobuf on 5.x, but this makes integration with newer protobuf ecosystem packages harder.

Environment observed:

• aliyun-log-python-sdk: 0.9.46
• Resolved protobuf due to this constraint: 5.29.6
• Python: 3.13 / 3.14

Related older protobuf compatibility issues exist, but they appear to target protobuf 4-era breakage rather than the current upper-bound constraint for protobuf 6/7 compatibility.

No dependency file or test is named in the issue. Start by locating the package metadata that declares the protobuf range, then run the existing test suite against protobuf 6 and 7; done means a validated compatible upper bound without breaking the SDK.