chore: remove file sync log spam and unused logs command

[tusharmath]

Summary

Remove noisy log spam from the file sync pipeline and drop the unused forge logs CLI command.

Context

Two sources of high-frequency log noise were identified:

1. File sync logs: Every file processed during workspace indexing emitted two INFO log lines — "File sync started" and "File sync completed". For a workspace with hundreds or thousands of files, this produced thousands of redundant log entries per sync cycle, drowning out meaningful log output.

2. forge logs command: The forge logs CLI subcommand and its supporting module (logs.rs, LogsArgs) were added to stream/tail forge log files. The command has since become unnecessary and was removing dead weight from the binary and CLI surface.

Changes

• Removed "File sync started" and "File sync completed" info! log calls from the batch file sync loop in crates/forge_services/src/sync.rs
• Deleted the forge logs CLI subcommand (TopLevelCommand::Logs) and its LogsArgs struct from crates/forge_main/src/cli.rs
• Deleted crates/forge_main/src/logs.rs (the entire log-tailing module)
• Removed the mod logs declaration and the TopLevelCommand::Logs dispatch arm from crates/forge_main/src/lib.rs and ui.rs

Testing

# Verify the project compiles cleanly
cargo check

# Confirm the logs subcommand is gone
cargo run -- --help   # should not list a "logs" subcommand

# Run existing tests
cargo insta test --accept