chore: make the already signed log debug level

[rach-id]

Overview

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

Summary by CodeRabbit

• Refactor
  • Adjusted logging levels for routine operations to reduce noise in application logs, enhancing the clarity of important information for users monitoring system activity.

[coderabbitai]

Walkthrough

The update involves modifying the logging level for certain operations within the Orchestrator component. Messages that pertain to the signing of validator sets and data commitments are now logged at a "Debug" level instead of "Info," indicating a shift towards less verbose logging during normal operations.

Changes

File	Change Summary
orchestrator/orchestrator.go	Changed logging level from "Info" to "Debug" for already signed valsets and data commitments.

🐇 In the code where logs abound, 🍂
A quieter space we've now found. 🌙
As autumn leaves twirl to the ground,
Our logs whisper with lesser sound. 🍁

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 1108ada and 9cb3fdc.

Files selected for processing (1)

• orchestrator/orchestrator.go (2 hunks)

Files skipped from review due to trivial changes (1)

• orchestrator/orchestrator.go