Detect and migrate static plugin usages

[philipp-spiess]

This PR builds on top of the new JS config to CSS migration and extends it to support migrating static plugins.

What are static plugins you might ask? Static plugins are plugins where we can statically determine that these are coming from a different file (so there is nothing inside the JS config that creates them). An example for this is this config file:

import typographyPlugin from '@tailwindcss/typography'
import { type Config } from 'tailwindcss'

export default {
  content: ['./src/**/*.{js,jsx,ts,tsx}'],
  darkMode: 'selector',
  plugins: [typographyPlugin],
} satisfies Config

Here, the plugins array only has one element and it is a static import from the @tailwindcss/typography module. In this PR we attempt to parse the config file via Tree-sitter to extract the following information from this file:

• What are the contents of the plugins array
• What are statically imported resources from the file

We then check if all entries in the plugins array are either static resources or strings (something I saw working in some tests but I’m not sure it still does). We migrate the JS config file to CSS if all plugins are static and we can migrate them to CSS @plugin calls.

[philipp-spiess]

(Purposely not adding a change log since it's still covered in the initial JS config => CSS change log entry)

[philipp-spiess]

Can also be default

[philipp-spiess]

Will add support for this in a follow-up:

import typography from '@tailwindcss/typography'

plugins: [
  require('@tailwindcss/typography')({
      className: 'wysiwyg',
    }),
   typography({
      className: 'wysiwyg',
    })
]