Springcloud dual registration scenario, DiscoveryClientInterceptor/DiscoveryClientServiceInterceptor can be optimized

[provenceee]

What would you like to be added?

Optimize com.huawei.registry.interceptors.DiscoveryClientInterceptor/DiscoveryClientServiceInterceptor

Why is this needed?

Currently, these two interception points call this method again in the interception point logic, and then use thread variables to exit. You can consider putting the logic of merging instances into the post-interception point and removing the thread variables. In addition, in the webflux scenario, use block is forced to block, you can consider changing it to non-blocking merge