[classnames] unify import name

[tay1orjones]

We're not using a consistent name for usages of the classnames package.

import cn from 'classnames';
import cx from 'classnames';
import classnames from 'classnames';
import classNames from 'classnames';

We need to decide on one and refactor all usages to fall in line.

[sstone2423]

Looks like cx and classNames are used by the package's README.

I'd suggest classNames, just to keep it obvious.

[tay1orjones]

There might be an eslint rule we could employ to help drive this consistency. We should do some research. Not a requirement by any means though.

[tay1orjones]

🎉 This issue has been resolved in version 2.94.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀