[BUG] `no-custom-classname` rules prevents `migration-from-tailwind-2` rule

[francoismassart]

Describe the bug

You will not get errors messages from migration-from-tailwind-2 like
Classname 'flex-shrink-0' should be updated to ' shrink-0' in Tailwind CSS v3!

To Reproduce
Having both rules enabled:

• no-custom-classname
• migration-from-tailwind-2

You will not get errors messages from migration-from-tailwind-2 like
Classname 'flex-shrink-0' should be updated to ' shrink-0' in Tailwind CSS v3!

Expected behavior
Rule migration-from-tailwind-2 should detect if no-custom-classname is enabled, if so, it should add specific values (outdated classnames from TailwindCSS v2 to the whitelist option of the no-custom-classname rule.

Additional context
Another workaround is to:

1. temporary turn off no-custom-classname rule
2. fix the errors from migration-from-tailwind-2
3. finally turn back on no-custom-classname rule