fix: workaround to resolve core-js path error bug

[PeachScript]

Checklist

• npm test passes
• commit message follows commit guidelines

Description of change

Process require statements in core-js lock plugin, but the real reason that caused the import statements transform to require statements still not found.

• close [Bug] 通过cnpm下载v2版本，为啥依赖的corejs下载的是v3.7.0的版本了？最近很多老项目编译都有问题了 #5715

[sorrycc]

还是得找到根源，谁改的 import -> require 。

[PeachScript]

还是得找到根源，谁改的 import -> require 。

是的，主要现在答疑人数激增，先把问题 workaround 掉，我们在持续排查

[afc163]

看看 babel/babel#12340 有没有关系？

[ycjcl868]

看看 babel/babel#12340 有没有关系？

可能相关

umi 的复现 demo： https://github.com/ycjcl868/umi-2-core-js-bug

[ycjcl868]

确认了，是这一行导致 babel/babel#12331

[nicolo-ribaudo]

Not directly related to this bug, but you can probably remove this custom plugin by doing something like storybookjs/storybook#13055 (so that Babel already inject imports to the correct core-js path).