fix: linux musl resolve failed

[jerrykingxyz]

Summary

Some linux musl can not get create time, and it will make resolve failed because of metadata return err.

This PR will specify a default value of 0 for the creation time when the platform does not support it.

Should fix:

• [Bug]: Tsconfig not found issue during build rsbuild#3994
• Error: [html-rspack-plugin]: Child compilation failed: rspress#1593
• rsbuild@1.1.0 doesn't work in my ci and throws an error: “Tsconfig not found” rsbuild#3985
• [Bug]: ERROR in × Module not found: Can't resolve './src/main.tsx' in #8446
• [Bug]: Module not found: Can't resolve <entry_path> in Docker #8433

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rspack canceled.

Name	Link
🔨 Latest commit	c000bcd
🔍 Latest deploy log	https://app.netlify.com/sites/rspack/deploys/673bc8ba07f4060008add755

[hardfist]

why the resolve succeed before and dont get the panic message now

[jerrykingxyz]

why the resolve succeed before and dont get the panic message now

Before #8366, We use rspack_resolver::FileMetadata::from with std::fs::Metadata and it does not get the metadata.created() values.

code:
https://github.com/web-infra-dev/rspack/pull/8366/files#diff-bf8cd6ecce0c487ed3834f3fa4e20f4bdde318d99fc6f2ff75a49a6e08307948L22

Currently we will convert std::fs::Metadata -> rspack_fs::FileMetadata -> rspack_resolver::FileMetadata, and this error occurs during the first conversion.