chore: use lodash-es to support vite

[CarterLi]

This is a ...

• New feature
• Bug fix
• Site / document update
• Component style update
• TypeScript definition update
• Refactoring
• Code style optimization
• Branch merge
• Other (about what?)

What's the background?

1. Describe the source of requirement.
2. Resolve what problem.
3. Related issue link.

We still use lodash, which uses the old commonjs module system and doesn't play well with vite.

Which results the errors: Uncaught (in promise) SyntaxError: The requested module '/@modules/lodash/isPlainObject.js' does not provide an export named 'default'

This PR replace all uses of lodash to lodash-es

API Realization (Optional if not new feature)

1. Basic thought of solution and other optional proposal.
2. List final API realization and usage sample.
3. GIF or snapshot should be provided if includes UI/interactive modification.

What's the effect? (Optional if not new feature)

1. Does this PR affect user? Which part will be affected?
2. What will say in changelog?
3. Does this PR contains potential break change or other risk?

Shouldn't have any behavior change

Changelog description (Optional if not new feature)

1. English description
2. Chinese description (optional)

1. chore: use lodash-es to support vite
2. 事务性：使用 lodash-es 以支持 vite

Self Check before Merge

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• TypeScript definition is updated/provided or not needed
• Changelog is provided or not needed

Additional Plan? (Optional if not new feature)

If this PR related with other PR or following info. You can type here.

[TonyLuo]

vite 报错：
(index):1 Uncaught SyntaxError: The requested module '/@modules/tinycolor2/tinycolor.js' does not provide an export named 'default'

[CarterLi]

还有raf也报错。。。

[tangjinzhou]

vite 用的什么版本，哪个组件报错，新开issue 反馈吧 @TonyLuo @CarterLi

[tangjinzhou]

其实 lodash 在我这里也没有问题 😅

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.