[improve][meta] Support tuning Oxia MetadataStoreConfig through metadata-store URIs

[void-ptr974]

Fixes #26060

Motivation

When Oxia is used as the metadata store for BookKeeper through bookkeeperMetadataServiceUri / BookKeeper metadataServiceUri, there is currently no way to tune Pulsar MetadataStoreConfig settings for the metadata store created by the metadata-store: BookKeeper driver.

This makes it hard to tune Oxia metadata-store behavior such as batching delay, batching limits, session timeout, and SerDes threads without adding new BookKeeper-specific configuration fields.

Modifications

Add support for configuring MetadataStoreConfig through query parameters on metadata-store: URIs.

For example:

bookkeeperMetadataServiceUri=metadata-store:oxia://oxia-server:6648/bookkeeper?batchingMaxDelayMillis=10&batchingMaxSizeKb=256&numSerDesThreads=4

The Pulsar BookKeeper metadata driver now:

• Parses query parameters from metadata-store: URIs when it creates a metadata store.
• Consumes recognized MetadataStoreConfig parameters into the MetadataStoreConfig builder.
• Preserves unrecognized query parameters and passes them through to the underlying metadata store provider for future provider-specific extensions.
• Separates URI/query parsing from MetadataStoreConfig parameter binding, keeping the driver path focused on metadata-store creation.
• Keeps the existing shared METADATA_STORE_INSTANCE path unchanged, so the default broker path that reuses the broker metadata store is not affected.
• Reports configuration errors with context including the original metadataServiceUri and, when available, the backend metadata store URL.

The supported MetadataStoreConfig query parameters are:

allowReadOnlyOperations
batchingEnabled
batchingMaxDelayMillis
batchingMaxOperations
batchingMaxSizeKb
configFilePath
fsyncEnable
numSerDesThreads
sessionTimeoutMillis

The broker and BookKeeper configuration examples were updated to document the new URI query format.

Verifying this change

• Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

• Added AbstractMetadataDriverTest to verify URI parsing, MetadataStoreConfig query binding, unknown-parameter pass-through, default URI behavior, shared-store compatibility, and contextual validation failures.
• Extended broker configuration tests to verify bookkeeperMetadataServiceUri with query parameters is preserved and passed to BookKeeper client configuration.

Verified locally with:

./gradlew :pulsar-metadata:test --tests org.apache.pulsar.metadata.bookkeeper.AbstractMetadataDriverTest --max-workers=1 -PtestRetryCount=0
./gradlew :pulsar-metadata:checkstyleMain :pulsar-metadata:checkstyleTest --max-workers=1
./gradlew :pulsar-broker:test --tests org.apache.pulsar.broker.BookKeeperClientFactoryImplTest --tests org.apache.pulsar.common.naming.ServiceConfigurationTest --max-workers=1 -PtestRetryCount=0

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

• 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

This affects deployment configuration for users who explicitly configure metadata-store: URIs, especially Oxia-backed BookKeeper metadata stores. Existing configurations without query parameters and the default shared metadata-store path remain unchanged.

[lhotari]

LGTM

[mattisonchao]

Hi @void-ptr974

It seems like we need to refine the title and description since this change affects the whole metadata, not only Oxia. right?
Maybe also need to refine the configuration description.

Cc @lhotari

[lhotari]

Cherry-picked to branch-4.2 in #26150