Fix module entry point by migrating to vite for ESM building

[susnux]

☑️ Resolves

This introduces vite for building the module entry point instead of webpack.

1. The previously generated module by webpack is invalid as it still uses require instead of import which is not defined for ES modules.
2. Build time is much shorter
3. The resulting file is only 600 kiB instead of 930 kiB

(Different from #3529 as this just introduces vite for module building to fix the assets)

🏁 Checklist

• ⛑️ Tests are included or are not applicable
• 📘 Component documentation has been extended, updated or is not applicable

[ShGKme]

Cannot we make a full migration to Vite?
Or fix the problem with Webpack config, if possible.

I'm a bit afraid of having 2 (almost 3) different bundlers at the same time in terms of config support.

[skjnldsv]

Cannot we make a full migration to Vite? Or fix the problem with Webpack config, if possible.

I'm a bit afraid of having 2 (almost 3) different bundlers at the same time in terms of config support.

I think the goal is to do a step-by-step migration :)

[susnux]

Cannot we make a full migration to Vite?

That was / is my plan, but currently it does not work out that good because styleguide does not work that well with vite currently (see #2959 and #3529 and #3565 ).
So I wanted to first migrate this part to fix the module bundle, and then later migrate the other part.

(edit:)

I think the goal is to do a step-by-step migration :)

Exactly from those three previous PRs I know that doing all in one is quite hard and error prone, so doing it step by step seems to be the best way :)