chore(logging): replace std print lines with tracing logging

What does this MR do and why?

Deals with the tech debt of using println or eprintln statements instead of tracing calls. We should avoid using direct writes to STD as this bypasses our tracing formatter rules, log level rules and does not log to the log file.

Related Issues

[logging] Cleanup print lines and formatting (#32 - closed)

Testing

Full indexing was performed to verify code still compiles and runs.

Performance Analysis

Performance Checklist

• Have you reviewed your memory allocations to ensure you're optimizing correctly? Are you cloning or copying unnecessary data?
• Have you profiled with cargo bench or criterion to measure performance impact?
• Are you using zero-copy operations where possible (e.g., &str instead of String, slice references)?
• Have you considered using Cow<'_, T> for conditional ownership to avoid unnecessary clones?
• Are iterator chains and lazy evaluation being used effectively instead of intermediate collections?
• Are you reusing allocations where possible (e.g., Vec::clear() and reuse vs new allocation)?
• Have you considered using SmallVec or similar for small, stack-allocated collections?
• Are async operations properly structured to avoid blocking the executor?
• Have you reviewed unsafe code blocks for both safety and performance implications?
• Are you using appropriate data structures (e.g., HashMap vs BTreeMap vs IndexMap)?
• Have you considered compile-time optimizations (e.g., const fn, generics instead of trait objects)?
• Are debug assertions (debug_assert!) used instead of runtime checks where appropriate?