chore: remove redundant console logs

[VisargD]

Description

Motivation

Removing redundant console logs from retry handler

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

How Has This Been Tested?

• Unit Tests
• Integration Tests
• Manual Testing

Screenshots (if applicable)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Related Issues

[matter-code-review]

Summary By MatterAI

🔄 What Changed

Removed redundant console logs from the retry handler implementation. The PR removes 4 lines of console logging that were no longer needed in the retry handler functionality.

🔍 Impact of the Change

This change improves code cleanliness by removing unnecessary logging statements. It has no functional impact on the application behavior but makes the codebase more maintainable and reduces noise in the logs.

📁 Total Files Changed

• src/handlers/retryHandler.ts: Removed 4 console.log statements from the retry handler implementation

🧪 Test Added

N/A - This is a simple cleanup change that doesn't require additional tests.

🔒Security Vulnerabilities

N/A - No security implications.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

How Has This Been Tested?

• Manual Testing

Screenshots (if applicable)

N/A

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Related Issues

N/A

Tip

Quality Recommendations

1. Consider adding a comment explaining why the console logs were removed to provide context for future developers

[matter-code-review]

This PR removes redundant console logs from the retry handler, which is a good cleanup. The code changes look straightforward and appropriate.