make logger more clear with highlight component and use package name for default component

[cytown]

make logger more clear with highlight component and use package name for default component.

detail see screenshot

📝 Description

🗣️ Type of Change

• 🐞 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 📖 Documentation update
• ⚡ Code refactoring (no functional changes, no api changes)

🤖 AI Code Generation

• 🤖 Fully AI-generated (100% AI, 0% Human)
• 🛠️ Mostly AI-generated (AI draft, Human verified/modified)
• 👨‍💻 Mostly Human-written (Human lead, AI assisted or none)

🔗 Related Issue

📚 Technical Context (Skip for Docs)

• Reference URL:
• Reasoning:

🧪 Test Environment

• Hardware:
• OS:
• Model/Provider:
• Channels:

📸 Evidence (Optional)

Click to view Logs/Screenshots

☑️ Checklist

• My code/docs follow the style of this project.
• I have performed a self-review of my own changes.
• I have updated the documentation accordingly.

[yinwm]

LGTM, nice improvement to log readability! The yellow component highlight and auto package name fallback make logs much easier to scan.

A few non-blocking suggestions for future consideration:

1. The hardcoded ANSI code in FormatPrepare (\x1b[33m) doesn't check if stdout is a TTY. When output is piped or redirected, the escape codes will appear as garbage. Consider checking term.IsTerminal(int(os.Stdout.Fd())) or the ConsoleWriter's NoColor field.

2. getPackageNameFromFile returns "." when called from a file in the project root (e.g., main.go). A special case for "." returning something like "main" would be cleaner.

3. Consider adding unit tests for getPackageNameFromFile to cover normal paths and edge cases.

None of these block merging — the change is clean and well-scoped. 🚀