[BUG] The `tailwindcss/no-custom-classname` rule does not respect the new line-height modifier from Tailwind 3.3
Describe the bug
The tailwindcss/no-custom-classname rule does not respect the new line-height modifier from Tailwind 3.3.
To Reproduce Steps to reproduce the behavior:
- Go to https://play.tailwindcss.com/QJfwQ8NCak.
- Copy the markup into your project with
eslint-plugin-tailwindcsspreinstalled.
Expected behavior There should be no ESLint errors in the classes.
Screenshots

Environment (please complete the following information):
- OS: windows 10
- Softwares + version used:
- VSCode: 1.77.3
- Node.js: 16.14.2
- eslint-plugin-tailwindcss: 3.11.0
Also to add, same issue but it doesn't respect thebg-opacity old opacity modifier from the migration-from-tailwind-2 rule

Also to add, same issue regarding the extended fontFamily and colours. It does not recognised them anymore (they are properly listed in our config).
Note: tailwind config is now supported in TypeScript so we edit it to the TS version.

Also to add, same issue regarding the extended fontFamily and colours. It does not recognised them anymore (they are properly listed in our config).
Note: tailwind config is now supported in TypeScript so we edit it to the TS version.
upgrade to v3.12.0, then the plugin will get tailwind.config.ts.
I have 3.13.0 installed, but it doesn't seem the plugin is getting tailwind.config.ts
anyone with same issue ?