…dulesPlugin orderModules hook

Drop the optimization.cssModulesOrder option introduced in the previous commit
in favor of a more general SyncBailHook on CssModulesPlugin's compilation
hooks: orderModules(chunk, modules, compilation). Modules arrive pre-sorted by
full module name. A tap returning Module[] overrides the default import-order
topological sort (and so suppresses the "Conflicting order" warning); returning
undefined keeps the default. This avoids committing webpack core to a specific
ordering algorithm while still letting users (and dedicated plugins) solve the
discussion #20976 use case.

Add three configCases that exercise the new CssModulesPlugin orderModules hook:
- css-modules-order-priority: pin a specific file (e.css) to the front and
  keep the rest in name order — practical "reset.css first" pattern.
- css-modules-order-fallback: tap returns undefined and webpack falls back
  to its default import-order topological sort, including the Conflicting
  order warning (asserted via warnings.js).
- css-modules-order-multi-tap: two taps where the first wins and the second
  throws if reached, locking in SyncBailHook short-circuit semantics.

…ests

- Add JSDoc types (Compiler, Variant, CssCompilationHooks) so the file
  passes lint:types-test under TypeScript strict mode.
- Replace the Unix-only `endsWith("/e.css")` check in the "priority"
  variant with a cross-platform regex `/[\\/]e\.css$/` so the test also
  passes on windows-latest where module identifiers use backslashes.