feat: noValueAtRule css lint rule

[rishabh3112]

Summary

Implements noValueAtRule lint rule for css modules

TODO:

• Run this rule only when used inside css_modules (i.e. when enabled in parser options)
• Auto fixers - in seperate PR

Test Plan

• Add Snapshot tests for @value rule

Refers #3001

[denbezrukov]

Sorry, I forgot to mention that it seems now it's impossible to get a parser option inside in a rule.
I'd like to propose ignoring Rule this rule only when used inside css_modules (i.e. when enabled in parser options)

[rishabh3112]

@denbezrukov I would like to pick up autofixing as part of seperate PR. It seems to be much more involved. Adding findings here for future reference:

• Case 1 : Used for property values -> Simple fix
• Case 2 : For breakpoints in media queries -> Can't use CSS variables for it currently (ref: https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties).
• Case 3: For named value imports (Example: https://github.com/css-modules/css-modules/blob/master/docs/values-variables.md): No direct substitute I was able to find for this use-case. Please let me know if it exist.

[ematipico]

If you want to land the code action in another PR, I would suggest to not close the original issue or opening a new one.

[codspeed-hq]

CodSpeed Performance Report

Merging #3293 will not alter performance

_{Comparing rishabh3112:feat/no-value-at-rule-lint-rule (e2e9b7b) with rishabh3112:feat/no-value-at-rule-lint-rule (5683139)}

Summary

✅ 104 untouched benchmarks

[ematipico]

@rishabh3112

A couple of things:

• the categories are sorted alphabetically, probably this broke when merging the conflicts
• always run just gen-lint
• always run the tests with cargo t

[ematipico]

@rishabh3112 Thank you for your first contribution :) I merged the PR. We wait for your next PR for a code action