[improve][broker] Upgrade bookkeeper to 4.17.2/commons-configuration to 2.x/grpc to 1.72.0 and enable ZooKeeper client to establish connection in read-only mode

[StevenLuMT]

Background

Upgrade bookkeeper to 4.17.2

Modifications

1. [improve][broker] Upgrade bookkeeper to 4.17.2

2. [improve][build] Migrate deprecated commons-configuration 1.x to commons-configuration 2.x, base on Migrate deprecated commons-configuration 1.x to commons-configuration 2.x bookkeeper#4604
   2.1. import change: org.apache.commons.configuration to org.apache.commons.configuration2
   2.2. impl change: setDelimiterParsingDisabled(true) to setListDelimiterHandler(new DisabledListDelimiterHandler())

3. Enable ZooKeeper client to establish connection in read-only mode, base on Enable ZooKeeper client to establish connection in read-only mode bookkeeper#4244

4. Upgrade gRPC to 1.72.0 : grpc version match to bookeeper 4.17.2, base on Upgrade to grpc 1.72.0 bookkeeper#4591

Verifying this change

• Make sure that the change passes the CI checks.
  This change is a trivial rework / code cleanup without any test coverage.

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

Check the box below or label this PR directly.

Need to update docs?

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

Matching PR in forked repository

PR in forked repository: StevenLuMT#15

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.25%. Comparing base (bbc6224) to head (2d025b0).
⚠️ Report is 1250 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #24468      +/-   ##
============================================
+ Coverage     73.57%   74.25%   +0.67%     
+ Complexity    32624    32411     -213     
============================================
  Files          1877     1868       -9     
  Lines        139502   145762    +6260     
  Branches      15299    16701    +1402     
============================================
+ Hits         102638   108232    +5594     
- Misses        28908    28943      +35     
- Partials       7956     8587     +631     

Flag	Coverage Δ
inttests	26.66% <25.00%> (+2.07%)	⬆️
systests	23.32% <25.00%> (-1.00%)	⬇️
unittests	73.73% <100.00%> (+0.88%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...ookie/rackawareness/BookieRackAffinityMapping.java	78.08% <ø> (-1.36%)	⬇️
...in/java/org/apache/pulsar/PulsarBrokerStarter.java	43.19% <ø> (+6.06%)	⬆️
.../org/apache/pulsar/PulsarClusterMetadataSetup.java	72.43% <100.00%> (-0.09%)	⬇️
...ache/pulsar/broker/ManagedLedgerClientFactory.java	82.65% <ø> (-1.50%)	⬇️
.../prometheus/metrics/PrometheusMetricsProvider.java	71.87% <ø> (ø)
...ache/pulsar/zookeeper/LocalBookkeeperEnsemble.java	72.20% <ø> (-0.81%)	⬇️
...he/pulsar/metadata/impl/PulsarZooKeeperClient.java	44.61% <100.00%> (+2.89%)	⬆️

... and 1085 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lhotari]

Good work! However, I think we can split the common-lang -> commons-lang3 migration to a separate PR. In that separate PR it would also be useful to add check style rules that prevent using commons-lang for new code.

[StevenLuMT]

Good work! However, I think we can split the common-lang -> commons-lang3 migration to a separate PR. In that separate PR it would also be useful to add check style rules that prevent using commons-lang for new code.

@lhotari Good suggestion, I will split this out and submit a separate PR

[StevenLuMT]

Good work! However, I think we can split the common-lang -> commons-lang3 migration to a separate PR. In that separate PR it would also be useful to add check style rules that prevent using commons-lang for new code.

@lhotari Good suggestion, I will split this out and submit a separate PR

I have proposed a new one. After #24473 is merged, I will delete the duplicate code, rebase the master and push it again.

[StevenLuMT]

/pulsarbot run-failure-checks

[eolivelli]

LGTM

Please make it clear in the title that we are also updating other libraries

It would be better to split the patch, but I understand it is not possible

[frankjkelly]

Will this be backported to 3.3.X stream? If so can it receive those labels? Thanks!

[StevenLuMT]

Will this be backported to 3.3.X stream? If so can it receive those labels? Thanks!
Can the 3.3.x label be added directly, or do I need to initiate a vote? @lhotari @codelipenghui

[StevenLuMT]

Will this be backported to 3.3.X stream? If so can it receive those labels? Thanks!

Finished: two labels have been added, release/3.3.8 and release/4.0.6
Thanks @codelipenghui @frankjkelly

[StevenLuMT]

After bookeeper is upgraded, all org.apache.commons.lang references are removed, so the PR #24473 is also given the same label. Thanks @codelipenghui