feat:remove old zookeeper

[Stellar1999]

What is the purpose of the change

refer:#13960

Brief changelog

Verifying this change

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[Stellar1999]

Should the first CI test fix be merged, then rerun the test case for this PR. In my own repository, it has already passed.

[CrazyHZM]

The existence of ZookeeperTransporter is not very meaningful, so consider removing it.

[Stellar1999]

Please take another look. Do you think my code idea is correct? I removed the SPI and moved the ZookeeperTransporter to the module dubbo-remoting-zookeeper-curator5 in order to create an instance of Curator5ZookeeperTransporter. @CrazyHZM Thanks for your code review.

[CrazyHZM]

@Stellar1999 ZookeeperTransporter should be renamed ZookeeperClientManager or something else.
dubbo-remoting-zookeeper-api should also be incorporated into the curator5 module.

[Stellar1999]

Please take another look. Thanks for your guidance. @CrazyHZM
If it's alright, I will fix the sample test case.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 38.37%. Comparing base (a12975a) to head (cb220be).
Report is 1 commits behind head on 3.3.

Additional details and impacted files

@@            Coverage Diff             @@
##              3.3   #14028      +/-   ##
==========================================
- Coverage   38.55%   38.37%   -0.18%     
==========================================
  Files        1895     1893       -2     
  Lines       79272    79016     -256     
  Branches    11528    11502      -26     
==========================================
- Hits        30560    30321     -239     
- Misses      44439    44443       +4     
+ Partials     4273     4252      -21     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[CrazyHZM]

@Stellar1999
We should keep the dubbo-remoting-zookeeper-curator5 module and move the dubbo-remoting-zookeeper-api module into it.

[Stellar1999]

@Stellar1999 We should keep the dubbo-remoting-zookeeper-curator5 module and move the dubbo-remoting-zookeeper-api module into it.

Please take another look. Thanks for your guidance. @CrazyHZM

[AlbumenJ]

[CrazyHZM]

It all looks good at the moment, but recently, CI has not been very stable. Wait until CI is fully passed before merging.
@AlbumenJ

[AlbumenJ]

Please resolve conflicts

[sonarqubecloud]

Quality Gate passed

Issues
44 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud