plugins: Migrate plugins to vite

[sniok]

This PR continues vite migration. First part is in PR here #1981

Fixes this #1282

Testing done

• tested with examples, and plugins from plugin repo

[illume]

Can you please rebase against main?

(Also I'm not sure if that snyk check failing is still relevant? I thought you had made a change for that issue already?)

[illume]

Noticed a few things.

Seems the package exclude change needs to be added in here as well? (for the snyk license check)

[illume]

Are you sure this can be removed?

[sniok]

since it's a template for new plugins so I don't see a risk there. If storyshots plugin is deprecated I think it's fair for us to not support it. Keeping storyshots tests for plugins is not trivial, we would effectively need to maintain a copy of 'storyshots-tests' plugin that works with vite

[illume]

The issue for this is here: #1282 (should go in the PR description)

[illume]

Does this allow plugins to access environment variables at build time too? Here's the issue for that:

• environment variables not accessible by plugins #1894

(but it shouldn't block this PR being merged if it doesn't support it yet)

[sniok]

It does not provide process now and I'm not sure if it should. Plugin authors can use import.meta.env for env variables, and if they really need process they can install polyfill in the plugin

[sniok]

Rebased and fixed merge conflicts

[sniok]

Added interop: auto to the vite config that builds plugins

This allows plugins use default imports from pluginLib the same way webpack plugins do. It checks for the __esModule field and will get the default export.

Tested the Kompose plugin (built with vite) with main (vite) and with 0.24.1 (webpack)

With this change all combinations of webpack frontend, vite frontend, webpack plugin, vite plugin should work together

[sniok]

Did some additional testing
Collected some public plugins + example plugins (17 total) compiled all of them with vite and webpack separately.
Ran them on latest main and then 0.24.1 and I didn't see any obvious problem or crashes. Seems like we won't have to mark them as incompatible