Identify Webpack exiting configuration replacements for Vite

[cnotv]

Description

As we finally migrated to Vue3, migration to Vite is now possible but requires investigation over existing Webpack logic.

Context

Webpack NormalModuleReplacementPlugin

A particular attention will have to go to the Webpack configuration and the use of the NormalModuleReplacementPlugin() as it will have to be replaced by the Vite Plugin API (Thanks @catherineluse for the mention)

Webpack require.context()

In the project often, components are loaded globally or specifically in bulk. This has been already crossed as Webpack issue migrating from 4 to 5 (used by Vue3): #11773

Webpack VirtualModulesPlugin

TBD alternatives

Webpack BundleAnalyzerPlugin

TBD alternatives

CopyWebpackPlugin

TBD alternatives

[codyrancher]

Closing in favor of the epic since I'm attempting to do it as on merge. #7468