refactor: Classify must be rearchitected

Classify.rb is a pattern I borrowed from the Primer team but it's just not going to work for us. I've been really thinking about the best way to go about this to avoid duplication and be flexible and I believe the answer is sourcing class and constraints directly from the Tailwind config.

This presents some issues though bc the config is a JS file. I wrote a script to convert it to JSON but it's brittle and I don't love it.

I'm wondering if this would be a good use case for a JSON schema that we generate for each TW release and combine it with some of the `dry-rb` tools.

Open to suggestions but my goal is to separate (at minimum) the class config stuff into separate files based on their category on the Tailwind docs site.