feat: support require.ensure

[CPunisher]

Summary

closes #4304

Because rspack has not supported some API yet, this pr doesn't fully align require.ensure to webpack. But I think it's enough to use.

1. Webpack calls parser.in_scope when adding RequireEnsureItemDependency to depBlock. This API is marked as deprecated.
2. Webpack save dependencies and dependency block in nested block by setting parser.state.current = depBlock, which bundles the modules required in the success body to the created AsyncDependencyBlock. But rspack doesn't not support nested blocks yet.
   Related test case: https://github.com/web-infra-dev/rspack/tree/3beef37ec09a565da86b8211e6712655f6aefa32/tests/webpack-test/configCases/parsing/issue-14720
   Reated webpack issue: Inside require.ensure, using require with chained property causes dependencies to be added to wrong chunk webpack/webpack#14720

• The last test to update is: https://github.com/web-infra-dev/rspack/blame/5dd01e2abf32837b153d62ed64d1c0d1caaa299a/packages/rspack-test-tools/tests/statsOutputCases/limit-chunk-count-plugin/rspack.config.js#L1 by @SyMind

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rspack ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	2bb207e
🔍 Latest deploy log	https://app.netlify.com/sites/rspack/deploys/671519ae452f860008cd3c5c
😎 Deploy Preview	https://deploy-preview-7972--rspack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[LingyuCoder]

Perhaps some cases can be added to the runtime diff test to make sure that the generated runtime code is full aligned with webpack.

[LingyuCoder]

LGTM, thanks