[HBAR Rate Limit Redesign] Improive logging logic for hbarLimit related classes

[quiet-node]

Problem

Logging in the classes within the hbarLimiter repositories (e.g., EthAddressHbarSpendingPlanRepository, HbarSpendingPlanRepository, IPAddressHbarSpendingPlanRepository) appears to be duplicated and does not include a requestId. This makes it difficult to track logs during debugging.

Solution

Improve logging for HbarLimitter related classes

Alternatives

No response

[victor-yanev]

Already fixed in Kosi’s PR #2939

[victor-yanev]

Okay, nvm it seems that these changes were reverted in the PR, sorry!