feat: add log level guards to prevent unnecessary string generation

[belloibrahv]

Description:
This PR optimizes logging performance by implementing proper log level guards using Pino's isLevelEnabled API.
Changes made:

• Add isLevelEnabled checks before debug and trace logging calls
• Wrap existing debug/trace logs with level guards
• Implement consistent logging patterns across the codebase

Example of optimized logging:

if (cachedResponse) {
  if (this.logger.isLevelEnabled('debug')) {
    this.logger.debug(
      `${requestIdPrefix} getTransactionReceipt returned cached response: ${JSON.stringify(cachedResponse)}`,
    );
  }
  return cachedResponse;
}

if (!syntheticLogs.length) {
  if (this.logger.isLevelEnabled('trace')) {
    this.logger.trace(`${requestIdPrefix} no receipt for ${hash}`);
  }
  return null;
}

Related issue(s):
Fixes #1118

Notes for reviewer:

• The implemented guards prevent unnecessary string interpolation and JSON.stringify operations when debug/trace logging is disabled
• Pattern is consistently applied across debug and trace level logs
• No functional changes to the logging output - only performance optimization

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)
  • Verified log output with different log levels
  • Confirmed debug/trace messages are properly guarded
  • Tested with logging enabled and disabled to ensure proper functionality

[Nana-EC]

@belloibrahv you might want to rebase, there's a lot of unrelated changes that were pulled in

[belloibrahv]

@Nana-EC, I've rebased the branch and cleaned up the PR to only include the log level guard changes.

[Nana-EC]

@Nana-EC, I've rebased the branch and cleaned up the PR to only include the log level guard changes.

@belloibrahv please double check.
Looking at https://github.com/hashgraph/hedera-json-rpc-relay/pull/3154/files I'm still seeing 176 files getting changed, with many not relating to logs at all

[belloibrahv]

@ebadiere @quiet-node @shemnon @Nana-EC please help review my PR. Thank you

[quiet-node]

@belloibrahv hey thanks for the good work!

Looks like the DCO CI didn't pass due to this commit refactor: reduce code duplication in relay package didn't get signed off. Looking at the Details of the DCO job, it suggeests to run the commands below to fix it:

git rebase HEAD~7 --signoff
git push --force-with-lease origin issue-1118-log-level-guard

[belloibrahv]

@ebadiere @quiet-node @shemnon @Nana-EC please help review my PR. Thank you

[quiet-node]

heyy @belloibrahv thanks for updating the PR! However, the DCO still seems to fail. Also it seems like the PR now has some conflicts. Please Pull and resolve the conflicts.

[belloibrahv]

@Nana-EC @quiet-node @ebadiere @victor-yanev, I've been working to resolve the DCO (Developer Certificate of Origin) issues on this PR, but I'm encountering some challenges. The DCO check is failing due to incorrect sign-offs on several commits that were merged from the main branch.
I've tried the suggested approaches, including rebasing the branch and adding the sign-off manually, but I'm still running into problems. The commits from other authors seem to be the root cause, and I'm having difficulty properly resolving the sign-off discrepancies.
At this point, I would greatly appreciate if you could provide some guidance on how to best address this. I'm happy to work with you directly to find a solution, as I'm anxious to get this PR merged. Please let me know if you have any suggestions or if there's a better way I should be approaching this. Thank you for your understanding and assistance.

[Nana-EC]

@Nana-EC @quiet-node @ebadiere @victor-yanev, I've been working to resolve the DCO (Developer Certificate of Origin) issues on this PR, but I'm encountering some challenges. The DCO check is failing due to incorrect sign-offs on several commits that were merged from the main branch. I've tried the suggested approaches, including rebasing the branch and adding the sign-off manually, but I'm still running into problems. The commits from other authors seem to be the root cause, and I'm having difficulty properly resolving the sign-off discrepancies. At this point, I would greatly appreciate if you could provide some guidance on how to best address this. I'm happy to work with you directly to find a solution, as I'm anxious to get this PR merged. Please let me know if you have any suggestions or if there's a better way I should be approaching this. Thank you for your understanding and assistance.

HI @belloibrahv , you need to do a clean rebase.
This would mean this PR would have only your commits on top of the latest main branch, no others authors commit would be included and you wouldn't encounter any DCO given you sign and sign off.
If your branch actually includes others commits at this point it might be easier to do a new clean branch and add only your changes on top of it.
Your changes look good otherwise and we can merge this once all the steps are successful in CI.

[belloibrahv]

@Nana-EC @quiet-node @ebadiere @victor-yanev, I've been able to resolve the DCO, kindly help review the PR. Thank you.

[quiet-node]

@belloibrahv It appears your changes have broken the CI with the following error: src/lib/config/hbarSpendingPlanConfigService.ts(135,16): error TS2339: Property 'logger' does not exist on type 'typeof HbarSpendingPlanConfigService'. Please double-check.

[sonarcloud]

Quality Gate passed

Issues
5 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

[belloibrahv]

@Nana-EC @quiet-node @ebadiere @shemnon kindly help review the PR, Thank you.

[quiet-node]

@belloibrahv This line is causing the CI failures because this class doesn’t have a logger property. This can be easily fixed by using the logger instance from the arguments, which should resolve the CI issues.

Suggested change

	if (this.logger.isLevelEnabled('trace')) {
	if (logger.isLevelEnabled('trace')) {

[Nana-EC]

Nice catch @quiet-node.
@belloibrahv please run an npm run build-and-test before pushing to confirm everything builds and unit tests run well.
Looking forward to getting this PR in.
Thanks