API: Expose Naming Convention

[ryanfitzer]

This is NOT about making the names configurable. It would be great to have access to the naming conventions used by the Tailwind core plugins in order to use them across other implementations.

For example, I'd like to be able to have consistency across Tailwind classes and custom properties. There are certain situations, like theming components a multi-brand design system, where I wouldn't be able to use css classes and must rely on custom properties. In cases, I'd like to apply Tailwind's naming conventions in order to keep things intuitive.

I've looked through the codebase and noticed that these names are defined at the plugin level, aren't exported, and using multiple mechanisms (addUtilities(), createUtilityPlugin(), etc.).

Right now, I'm doing this manually. Not a huge issue, but would love to hear others thoughts on this.