[mattisonchao]

Motivation

Pulsar uses the Oxia Java client 0.10.3 (#27141). 0.10.4 is a patch release on top of it:

• The client no longer pushes its own library versions onto the applications that use it (oxia-client-java#489). 0.10.3 published its grpc, Netty, OpenTelemetry and JUnit BOMs as runtime platforms and declared grpc 1.84 and Netty 4.2, so Gradle builds against Pulsar 4.x, such as broker plugins, were lifted to grpc 1.84 and Netty 4.2. 0.10.4 declares the oldest versions it supports (grpc 1.75.0, Netty 4.1.139.Final, OpenTelemetry 1.62.0, protobuf 3.25.5) and tests the newest ones as well.
• list() and ListOption are deprecated in favor of rangeScan() (oxia-client-java#485), and a range scan can leave out the values (oxia-client-java#487).

Pulsar manages newer grpc, Netty, OpenTelemetry and protobuf versions itself, so the binary distribution keeps the same jars apart from the Oxia client.

Modifications

• Upgrade oxia in gradle/libs.versions.toml from 0.10.3 to 0.10.4.
• LICENSE.bin.txt: update the Oxia jars to 0.10.4.

OxiaMetadataStore still uses list() through ListOption, which now compiles with deprecation warnings. Moving it to rangeScan() is left to a follow-up.

Verifying this change

• Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as the Oxia tests in pulsar-metadata (OxiaMetadataStoreClosedClientTest, OxiaMetadataStoreScanByIndexTest, OxiaMetadataStoreSynchronizerTest, OxiaScanByIndexOutageTest, OxiaMetadataStoreErrorTest, OxiaPartitionKeyTest, OxiaSequenceKeysTest), which pass with 0.10.4. ./gradlew checkBinaryLicense passes.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment