improve tailwind-checker script

**for reference:** https://github.com/deco-cx/deco/pull/772
**proposal:**
- [ ] possibility of viewing the script result in a more user-friendly way in the admin, as a table. (idea: this could be a "dev app", something like a "dev-tools" category)
- [ ] recognize daisy ui
- [ ] if dynamic class exists in tailwind, suggest which one it would be and replace the dynamic class
- [ ] If a dynamic class repeats itself a lot, suggest a naming pattern to be followed

Start by reviewing the behavior and context in the referenced pull request #772, then locate the tailwind-checker script and its admin integration. Clarify which proposal is in scope before changing anything; done should include an agreed user-facing result and validation for the selected behavior.

Written by the indexing model from the issue text.