feat: Route event printing through logging

[priyansh4320]

Why are these changes needed?

All the event print() calls now use a logger instead of raw print, so you can control AG2’s output (format, handlers, filters, mute) with normal logging config.

Related issue number

#2175

Checks

• I've included any doc changes needed for https://docs.ag2.ai/. See https://docs.ag2.ai/latest/docs/contributor-guide/documentation/ to build and test documentation locally.
• I've added tests (if relevant) corresponding to the changes introduced in this PR.
• I've made sure all auto checks have passed.

[joggrbot]

📝 Documentation Analysis

All docs are up to date! 🎉

---

✅ Latest commit analyzed: 39ec903 | Powered by Joggr

[codecov]

Codecov Report

❌ Patch coverage is 94.93671% with 4 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
autogen/logger/logger_utils.py	89.47%	2 Missing and 2 partials ⚠️

Files with missing lines	Coverage Δ
autogen/events/agent_events.py	97.21% <100.00%> (-0.43%)	⬇️
autogen/events/base_event.py	90.19% <100.00%> (+0.61%)	⬆️
autogen/events/client_events.py	90.32% <100.00%> (ø)
autogen/events/print_event.py	75.00% <100.00%> (ø)
autogen/logger/logger_utils.py	93.10% <89.47%> (-6.90%)	⬇️

... and 18 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.