In `import/order`, modules starting with `@/` are always treated as `unknown`

[ykzts]

If you run yarn lint on https://github.com/ykzts-sandbox/nextjs-with-module-path-aliases, you will get the following output.

$ yarn lint
yarn run v1.22.11
$ next lint
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5

./pages/index.tsx
5:1  Error: `../styles/Home.module.css` import should occur before import of `@/components/hello`  import/order

info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

regression from #2146

[ljharb]

The order rule should likely use the resolver to get the type.

[rygine]

This bug seems to also be present in the no-internal-modules rule. I'm getting back unknown for aliased paths.

[karl-run]

Seeing it both with NextJS' default "paths": { "@/*": ["./src/*"] } as well as Remix' default "paths": { "~/*": ["./src/*"] }.