Remix compiler always bundles tsconfig path aliases

[ilijaNL]

What version of Remix are you using?

2.2.0

Are all your remix dependencies & dev-dependencies using the same version?

• Yes

Steps to Reproduce

1. Create a monorepo without hoisting (default pnpm workspaces)
2. Create a package @my-company/a
3. Install some 3rd party dependencies to the @my-company/a package, say lodash and use it somewhere in code
4. Create an remix app in monorepo and add the @my-company/a as a dependency ("@my-company/a": "workspace:*")
5. Add path alias in tsconfig which targets the workspace package:

 "paths": {
      "~/*": ["./app/*"],
      // this somewhoe doesnt work
      "@my-company/a": ["../../packages/my-company/a/src"]
    },

6. Try to run (dev) the remix app.
7. Inspect the build/index.js: All the code from packages/my-company/a/src is bundled. This will result in importing dependencies of the @my-company/a package such as lodash which does not exist in node_modules of remix app

Expected Behavior

If the path aliasing matches a dependency, don't bundle the local package.
So in the end, the remix compiler should not bundle @my-company/a if @my-company/a is defined as a dependency in package.json of the app

Actual Behavior

The remix compiler bundles the monorepo package if path aliasing is used and doesn't respect the package.json dependencies.

related to #1405 and #2412