Fix encoding issue in file writing to handle Non-ASCII characters

[splendid-pilot]

Description:
This PR fixes a UnicodeEncodeError in line_profiler when profiling functions with non-ASCII characters (e.g., CJK characters) in function names or docstrings. The error occurs on Windows due to the default cp1252 encoding not supporting such characters.

Solution: The fix explicitly sets encoding='utf-8' in the write_text function calls in explicit_profiler.py, ensuring proper handling of non-ASCII characters during profiling output.

Why:
Ensures line_profiler works correctly with CJK and other non-ASCII characters, especially on Windows systems.
Prevents crashes when profiling functions with non-Latin characters in their names or docstrings.

[Erotemic]

Ah Windows encoding issues. Such a pain.

LGTM. I'll merge once dashboards pass.

[Erotemic]

I need to merge the 1.4.2 branch, after that point we will rebase on top of main and then add a CHANGELOG note. Then this will be merged into main and be part of the next patch release.

By default I'll wait for other PRs before I make a release, but if this is causing day-to-day issues, let me know and I can expedite the process.

[Erotemic]

did not mean to close this, reopened here: #313

[splendid-pilot]

No problem at all, and thank you for addressing the issue. I’ve already applied the change in my local environment, so there’s no need to expedite the process. Thanks again for your time and for maintaining this great project!