[Feature]: improve error message when importing uri like request, eg virtual:uno.css, that cannot be resolved

[xc2]

What problem does this feature solve?

Source

// case 1 typicall happens on migrating from other builders
import "virtual:uno.css"
// case 2 and 3
import * as NodeFS from "node:fs" // target: "web"
import * as BunFS from "bun:fs" // target: "web"

Got

Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  content should be available
Location: /Users/webinfra/ec2-macos-ci-0/_work/rspack/rspack/crates/rspack_loader_runner/src/runner.rs:446

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 1: _napi_register_module_v1
    at <unknown source file>
 2: _napi_register_module_v1
    at <unknown source file>
 3: _napi_register_module_v1
    at <unknown source file>
 4: _napi_register_module_v1
    at <unknown source file>
 5: _napi_register_module_v1
    at <unknown source file>
 6: _wasmer_vm_imported_memory32_atomic_notify
    at <unknown source file>
 7: _napi_register_module_v1
    at <unknown source file>
 8: _napi_register_module_v1
    at <unknown source file>
 9: _napi_register_module_v1
    at <unknown source file>
10: _napi_register_module_v1
    at <unknown source file>
11: _napi_register_module_v1
    at <unknown source file>
12: _napi_register_module_v1
    at <unknown source file>
13: _napi_register_module_v1
    at <unknown source file>
14: _napi_register_module_v1
    at <unknown source file>
15: _napi_register_module_v1
    at <unknown source file>
16: _napi_register_module_v1
    at <unknown source file>
17: _napi_register_module_v1
    at <unknown source file>
18: __pthread_start
    at <unknown source file>
 ELIFECYCLE  Command failed.

What does the proposed API of configuration look like?

Expected

Something more friendly that telling what happened and recommended solution

[SoonIter]

After #6404, it seems this issue has been solved