Remove debug logs for successful query of members

[dcorbacho]

It just floods the logs on any long run. Just leave the failure ones.

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +1.34 🎉

Comparison is base (90efd62) 90.96% compared to head (afbbffa) 92.31%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #208      +/-   ##
==========================================
+ Coverage   90.96%   92.31%   +1.34%     
==========================================
  Files          16       21       +5     
  Lines        2868     4917    +2049     
==========================================
+ Hits         2609     4539    +1930     
- Misses        259      378     +119     

Flag	Coverage Δ
erlang-24	91.33% <ø> (+1.62%)	⬆️
erlang-25	91.31% <ø> (+1.81%)	⬆️
erlang-26	88.85% <ø> (?)
os-ubuntu-latest	92.23% <ø> (+1.33%)	⬆️
os-windows-latest	91.25% <ø> (+1.74%)	⬆️

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

Impacted Files	Coverage Δ
src/khepri_cluster.erl	80.88% <ø> (+0.68%)	⬆️

... and 16 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[dumbbell]

Because it is not a cheap call, I wanted to keep them around until we have something lighter to query cluster members. What do you think? I say that, but I don't have an implementation idea yet.

[dcorbacho]

If you have any use for the logs, just leave them. But the issue I have is not with the query itself, but the huge logs it generates where this repeated line just becomes noise. It needs to be filtered out every time to find the relevant information on the logs.

[dumbbell]

Ok, if it's painful, let's remove them. I will take note that RabbitMQ calls this way too often, currently causing delays, and that this must be investigated.