fix!: paths match align with tsconfig-paths-webpack-plugin

[stormslowly]

⚠️ Note
This PR will introduce Breaking Change‼️

When there is no references configed, take the demo repo struct as an example.
app uses codes from project-a, they both config paths as "foo": ["./mock_foo"] in tsconfig.json

├── app
│   ├── mock_foo
│   │   └── index.js
│   ├── src
│   │   └── index.ts
│   ├── tsconfig.json
│   └── webpack.config.js
└── project-a
    ├── index.js
    ├── mock_foo
    │   └── index.js
    ├── src
    │   └── index.ts
    └── tsconfig.json

before

paths alias takes effect on files under project folder only.
for example
in app/src/index.ts, resolve "foo" will return app/mock_foo/index.js
in project-a/src/index.ts, resolve "foo" will return NotFound Error
see the example in spack_resolver_demo.js in demo repo

after

paths alias takes effect on all files. (tsconfig-paths-webpack-plugin dose so)
take previous exmaple, resolving "foo" in project-a/src/index.ts will return app/mock_foo/index.ts.

close: #74

[codspeed-hq]

CodSpeed Performance Report

Merging #74 will not alter performance

_{Comparing fix/align_paths_match_with_tsconfig_paths (806438d) with main (1ab1bd9)}

Summary

✅ 3 untouched benchmarks

[hardfist]

this is a breaking change and should add breaking notice in description, and also please add reference to the semantic description of tsc and webpack-tsconfig-paths-plugins