fix: use PathBuf instead of String to compatible different platforms and non-Unicode sequences in filepath

[dyxushuai]

The different between platforms: ^1

The need for this type arises from the fact that:

1. On Unix systems, strings are often arbitrary sequences of non-zero bytes, in many cases interpreted as UTF-8.

2. On Windows, strings are often arbitrary sequences of non-zero 16-bit values, interpreted as UTF-16 when it is valid to do so.

3. In Rust, strings are always valid UTF-8, which may contain zeros.

Non-Unicode sequences: ^2

use std::path::Path;

let path = Path::new("foo.txt");
assert_eq!(path.to_string_lossy(), "foo.txt");
// "fo�.txt"

[dyxushuai]

@Wollac needs your review

[Wollac]

I agree that PathBuf is the cleaner way to go here. So let's fix the remaining issues to get this merged.

[dyxushuai]

I agree that PathBuf is the cleaner way to go here. So let's fix the remaining issues to get this merged.

Already fixed all tests and rebase to the newest main branch, @Wollac pls give another look.