optimize: use curator instead of zkclient in registry model

[leizhiyuan]

• I have registered the PR changes.

Ⅰ. Describe what this PR did

fixes #6772

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?

there has been

Ⅳ. Describe how to verify it

ZookeeperRegisterServiceImplTest

Ⅴ. Special notes for reviews

merge after #6779

[codecov]

Codecov Report

Attention: Patch coverage is 58.82353% with 42 lines in your changes missing coverage. Please review.

Project coverage is 52.33%. Comparing base (be01fb0) to head (23329bd).
Report is 1 commits behind head on 2.x.

Files with missing lines	Patch %	Lines
...very/registry/zk/ZookeeperRegisterServiceImpl.java	58.82%	38 Missing and 4 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##                2.x    #6831      +/-   ##
============================================
+ Coverage     52.30%   52.33%   +0.02%     
- Complexity     6405     6416      +11     
============================================
  Files          1083     1083              
  Lines         37846    37913      +67     
  Branches       4489     4492       +3     
============================================
+ Hits          19795    19841      +46     
- Misses        16081    16103      +22     
+ Partials       1970     1969       -1     

Files with missing lines	Coverage Δ
...very/registry/zk/ZookeeperRegisterServiceImpl.java	57.76% <58.82%> (-5.55%)	⬇️

... and 6 files with indirect coverage changes

[funky-eyes]

ZkConfigurationTest.testRemoveConfig:119 expected: but was:
这个失败率非常高，得看下如何解决，不然合进去时不时就失败不太好

[leizhiyuan]

ZkConfigurationTest.testRemoveConfig:119 expected: but was: 这个失败率非常高，得看下如何解决，不然合进去时不时就失败不太好

最新的一次应该修复了

[funky-eyes]

ZkConfigurationTest.testRemoveConfig:119 expected: but was: 这个失败率非常高，得看下如何解决，不然合进去时不时就失败不太好

最新的一次应该修复了

ok

[funky-eyes]

LGTM