modularize_imports issue for re-export from node_modules

[tianyingchun]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

mac os/next 12.2.5

What browser are you using? (if relevant)

chrome

How are you deploying your application? (if relevant)

No response

Describe the Bug

next 12.2.5 follow this feature. #38583
mostly this feature works fine, except another sense has an issue here

for example

     '@mui/material': {
        transform: '@mui/material/{{member}}',
        preventFullImport: true,
      },

consider below sense:

1. import {alpha} from @mui/material
2. the alpha is re-exported from @mui/material

export {
 alpha
} from '@mui/system';

3. in fact the alpha is really existed in @mui/system
4. but in the next it will transform to @mui/material/alpha, this is wrong, it should ignore @mui/material/alpha because we won't configure the modularizeImports

Expected Behavior

in fact the alpha is really existed in @mui/system
but in the next it will transform to @mui/material/alpha, this is wrong, it should ignore @mui/material/alpha because we won't configure the modularizeImports

Link to reproduction

https://github.com/tianyingchun/next-issue

To Reproduce

1. yarn
2. yarn dev
3. see console
4. related feature: feat(next-swc/modularize_imports): Add Kebab case #38583

[dsiebes]

+1. This would be a very helpful for large projects based on MUI libraries or other large nested projects. Local dev can be quite a challenge given that we can not refactor all import statements or exports from dependencies. Thank you to anybody who takes a moment to look at this :)