feat: Add a lint for unsupported CSS Module selector

[kdy1]

Related: vercel/next.js#64299

I made it a parse error because the specification about it is ambiguous thus it's better to bail out.

[devongovett]

Thanks! Will do a release tomorrow.

[kdy1]

@devongovett Did you do a release?

[devongovett]

crates are now published. I ran into a CI build issue for the npm binaries that I still need to fix, but crates should be usable.

[kdy1]

Thank you!

[Baptistemontan]

Sorry to bother, but this should not have been a patch semver bump but a minor bump, the addition of a new variant to a public enum is breaking some builds. trunk can't be installed at the moment because it tries to make lightningcss alpha 55 works with parcel_selectors v0.26.6, and cause this error:

error[E0004]: non-exhaustive patterns: `&SelectorParseErrorKind::AmbiguousCssModuleClass(_)` not covered
   --> C:\Users\bapti\.cargo\registry\src\index.crates.io-6f17d22bba15001f\lightningcss-1.0.0-alpha.55\src\error.rs:266:11
    |
266 |     match &err {
    |           ^^^^ pattern `&SelectorParseErrorKind::AmbiguousCssModuleClass(_)` not covered
    |
note: `SelectorParseErrorKind<'_>` defined here
   --> C:\Users\bapti\.cargo\registry\src\index.crates.io-6f17d22bba15001f\parcel_selectors-0.26.6\parser.rs:188:1
    |
188 | pub enum SelectorParseErrorKind<'i> {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
201 |   AmbiguousCssModuleClass(CowRcStr<'i>),
    |   ----------------------- not covered
    = note: the matched value is of type `&SelectorParseErrorKind<'_>`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
    |
299 ~       SelectorParseErrorKind::ClassNeedsIdent(t) => SelectorError::ClassNeedsIdent(t.into()),
300 ~       &SelectorParseErrorKind::AmbiguousCssModuleClass(_) => todo!(),

[devongovett]

Ah sorry about that, I didn't realize it wasn't pinned. Not sure I can fix it at this point. Will be more careful in the future.