feat!: allow to run Babel on non js/ts extensions (fixes #38)

[ArnaudBarre]

This PR is currently composed of 3 commits:

• First, just skip everything if id include node_modules. Given that esbuild pre-bundle deps, it seems strange for me that you need to process them again via Babel. I'm not sure we should encourage people to rely on the fact that they use node_modules with non standard content
• Second, main commit: use the include/exclude like other plugins, with a default include that was the previous mandatory check. I don't see why you would want to skip fast refresh if it can be enable. This simplifies a lot the code and the configuration options compare to feat(plugin-react): change how babel.include/exclude options behave vite#6202. Finally I think that changing the behaviour when the import is outside vite root but still imported as source is confusing. I have bad memories of CRA disabling simple code sharing between two projects and requiring to setup a fake local lib.
• Third, add an mdx playground with a simple HMR test

Fixes #38, fixes #22, fixes #24 and should also fix #16

[patak-dev]

I think we should wait for this one a bit, given that the release of Vite 4 is so close. Now that the plugin is is in a separate repository we can do a new major for it independent of Vite after the holidays. We can do the a proper beta period and check with the ecosystem.

[sapphi-red]

I think this changes behavior when id is foo.txt?a=.jsx. (it was true but now it's false)