chore: improve documentation for lint rules

[mellyeliu]

Context

From discussions with ESLint oncall StyleX lint rules often provide lots of confusion, particularly around logical -> standard properties. We've previously added autofixes, but updating rules documentation here and internally to reduce confusion

Pre-flight checklist

• I have read the contributing guidelines
  Contribution Guidelines
• Performed a self-review of my code

[github-actions]

workflow: benchmarks/size

Comparison of minified (terser) and compressed (brotli) size results, measured in bytes. Smaller is better.

[email protected] size:compare
node size/compare.js /tmp/tmp.72rx9eVq8f /tmp/tmp.w1fBOUGA2U

Results	Base	Patch	Ratio
stylex/lib/stylex.js
· compressed	985	985	1.00
· minified	3,154	3,154	1.00
stylex/lib/StyleXSheet.js
· compressed	1,266	1,266	1.00
· minified	3,776	3,776	1.00
benchmarks/size/.build/bundle.js
· compressed	537,611	537,611	1.00
· minified	7,435,904	7,435,904	1.00
benchmarks/size/.build/stylex.css
· compressed	100,609	100,609	1.00
· minified	755,721	755,721	1.00

[necolas]

What does this mean?

[mellyeliu]

preferInline expands shorthands to standard logical equivalents when set to true, otherwise uses directional expansion (default).

ie.

//prefer-inline: true
margin: 10 15 20 25, 

marginTop: 10px;
marginRight: 15px;
marginBottom: 20px;
marginLeft: 25px;

//prefer-inline: false
margin: 10 15 20 25, 

marginTop: 10px;
marginInlineEnd: 15px;
marginBottom: 20px;
marginInlineStart 25px;

[necolas]

I see. Not the best name. The comment should probably say something like "Whether the expansion uses logical direction properties instead of physical"