Do not scan tailwind-merge sources for candidates

[philipp-spiess]

Resolves #15722

This PR adds a list of ignored dependencies (in the current form only tailwind-merge) to the Vite extension which, when included in the dependency tree, are no longer scanned by the Tailwind CSS compiler for candidates. This is to work around an issue where some dependencies contain vast lists of valid Tailwind CSS class names which would otherwise always be inlined in the build.

Test plan

This was tested in our Vite playground on both dev and prod builds across macOS and Windows:

Windows prod build before

Windows prod build after

This includes a debug console.log(…) to make sure it matches the right module.

Windows dev build after

This includes a debug console.log(…) to make sure it matches the right module.

[RobinMalfait]

Should we add an integration test to ensure this works as expected (and keeps working in the future)?

Otherwise, I like it.