fix(es/loader): Fix the absolute path check when resolving modules

[CPunisher]

fixes: #9854

if !module_specifier.starts_with('.') is true when module_specifier is neither a relative path nor an absolute path like classnames, then the file in current working directory will be found.

I gave up adding a test because it needs to change the current working directory (by calling std::env::set_current_dir), which causes failures of other tests.

Another changed line of code is to align with https://www.typescriptlang.org/docs/handbook/modules/reference.html#baseurl, which says:

The baseUrl compiler option can be combined with any moduleResolution mode and specifies a directory that bare specifiers (module specifiers that don’t begin with ./, ../, or /) are resolved from

[changeset-bot]

🦋 Changeset detected

Latest commit: 444c984

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codspeed-hq]

CodSpeed Performance Report

Merging #10080 will degrade performances by 5.69%

_{Comparing CPunisher:02-21-fix/module-resolve-1 (444c984) with main (a883cdc)}

Summary

❌ 1 regressions
✅ 190 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
❌	es/minifier/libs/moment	82.8 ms	87.8 ms	-5.69%