feat: add ability to log to a file

[carlosm27]

Description

This PR fixes #841

This PR adds the ability to create a log file.
This is an example of how to do it:

[vercel]

@carlosm27 is attempting to deploy a commit to the sparckles Team on Vercel.

A member of the Team first needs to authorize it.

[carlosm27]

Should we add the ability to add more configurations, like timestamps, levels, etc?

[codspeed-hq]

CodSpeed Performance Report

Merging #885 will not alter performance

_{Comparing carlosm27:log_file (6a5c4d5) with main (51bf8a3)}

Summary

✅ 146 untouched benchmarks

[sansyrox]

Hey @carlosm27 👋

How would you use this new interface?

[carlosm27]

Hey @carlosm27 👋

How would you use this new interface?

Hey @sansyrox. I would use it to create log files with timestamps, log level and with and add rotation policy.

What features are more appropiate for this interface?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
robyn	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 18, 2024 0:22am

[recurseml]

✨ No issues found! Your code is sparkling clean! ✨

[sansyrox]

Thanks for tackling this, @carlosm27 — file logging (#841) is genuinely useful and the FileHandler approach is the right idea. A couple of things before we can merge: the PR accidentally commits a compiled Windows binary (robyn/robyn.cp311-win_amd64.pyd) which needs to be removed, and the changes to integration_tests/index.py are demo snippets rather than an actual test. One functional concern: our log messages are wrapped with ANSI color codes via _format_msg, so they'd get written into the file as raw escape sequences — could you strip colors for the file handler? Finally, a quick rename to something like log_to_file would read more naturally. Happy to help get this over the line once those are addressed!