[fix][broker] fix the autoRecovery aware of the right rack info.

[yangl]

Fixes #18834 #18672

Motivation

When run the separate meta store between the Pulsar broker cluster and the Bookkeeper cluster, the metadataStoreUrl (broker .conf) different from the metadataServiceUri (bookkeeper.conf), the auto recovery (standlone) cannot get the right rack info because when we set the rack info by admin bookies set-bookie-rack, the rack info on the broker side, so we should get the rack info from the pulsar broker side, not the bookkeeper side.

Modifications

First get from the broker side，then downgrade to the old logic(bk side )

- String metadataServiceUri = ConfigurationStringUtil.castToString(conf.getProperty("metadataServiceUri"));
+ String metadataServiceUri = ConfigurationStringUtil.castToString(conf.getProperty("metadataStoreUrl"));

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

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

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: yangl#19

[horizonzy]

I recommend setting rack info in the bk zookeeper cluster.

[yangl]

I recommend setting rack info in the bk zookeeper cluster.

Of course, it would be best to migrate the Metadata BookieRackAffinityMapping strategy to the bookkeeper project so that bookkeeper-only businesses can have this capability as well.

[horizonzy]

cc @hangc0276

[hangc0276]

This logic is used for bk auto-recovery, and it doesn't make sense to get it from the Pulsar broker side. If we use it with this logic, we need to configure metadataStoreUrl in the conf/bookkeeper.conf

[yangl]

The current BookieRackAffinityMapping policy is implemented on the pulsar side and its configuration is configured to the pulsar's zk (metadatastore).
It would be best to migrate the Metadata BookieRackAffinityMapping strategy to the bookkeeper project so that bookkeeper-only businesses can have this capability as well.

[github-actions]

The pr had no activity for 30 days, mark with Stale label.