fix: Initialize default logger in AsyncPlaywrightCrawlerStrategy (#1704)

[YuriNachos]

Summary

• Initialize default AsyncLogger when no logger is provided to AsyncPlaywrightCrawlerStrategy
• Prevents NoneType errors when using custom crawler strategies with screenshots/PDFs

Fixes

Fixes #1704

Details

When users directly instantiate AsyncPlaywrightCrawlerStrategy without passing a logger, self.logger remains None. This causes crashes when the strategy attempts to log events, particularly during:

• Screenshot export
• PDF generation
• MHTML export

The fix initializes a default AsyncLogger(verbose=False) when no logger is provided, ensuring all logger calls succeed.

Root Cause

From the issue analysis:

• Users passing custom strategies to AsyncWebCrawler don't always provide loggers
• 47 places in the codebase call logger methods without null checks
• Only 8 places have null checks

Test plan

• Code review confirms the fix prevents NoneType errors
• Default logger is silent (verbose=False) to avoid unwanted output
• Existing behavior is preserved when logger is explicitly provided

🤖 Generated with Claude Code