feat(linter): implement noDuplicateProperties

[togami2864]

Summary

closes #2784

Test Plan

Added tests and snapshots

[codspeed-hq]

CodSpeed Performance Report

Merging #4029 will degrade performances by 19.13%

_{Comparing togami2864:2784 (b1ea322) with main (2035efe)}

Summary

⚡ 1 improvements
❌ 4 regressions
✅ 102 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	togami2864:2784	Change
❌	css_analyzer[bootstrap_18416142857265205439.css]	255.9 ms	304.3 ms	-15.92%
❌	css_analyzer[bulma_5641719244145477318.css]	784.5 ms	911.6 ms	-13.94%
❌	css_analyzer[foundation_11602414662825430680.css]	158.4 ms	183.9 ms	-13.82%
❌	css_analyzer[tachyons_11778168428173736564.css]	151.8 ms	187.7 ms	-19.13%
⚡	react.production.min_3378072959512366797.js[cached]	2 ms	1.8 ms	+7.5%

[dyc3]

Lets try to address the perf regression a little.

[dyc3]

You could add and use an alternative to to_ascii_lowercase_cow in biome_string_case eg to_lowercase_cow

[togami2864]

I think allmost part of this perf regression is caused by the use of the CSS Semantic Model. I'll see if there's room for performance improvement.

[ematipico]

I think allmost part of this perf regression is caused by the use of the CSS Semantic Model. I'll see if there's room for performance improvement.

We should really have a look at that, and understand if the cause is the semantic model or the rule.

You could create a "fake" rule that uses the semantic model, and always trigger the rule.

I believe it's important, because we don't have these kinds of regressions in the JavaScript rules, and when we do, it's usually caused by the business logic of the rule.