Reformat lmfdb/templates/style.css for readability

[roed-math]

Summary

Pure formatting cleanup of lmfdb/templates/style.css. No selector, declaration, value, comment, or rule order is changed — the rendered output should be byte-identical.

Standardized:

• 4-space indentation throughout (was a mix of 2/4 spaces)
• Opening brace on the same line as the selector, single space before
• Comma-separated selector lists split onto their own lines
• One declaration per line, single space after the colon
• Consistent blank-line spacing between rules
• Section banner comments grouping related rules (base, header, sidebar, properties box, forms, tables, knowls, front-page boxes, scroll wrappers, raw type-set, etc.)

Verified that, before and after the change, the multisets of:

• selectors (427)
• property declarations (1004)
• Jinja {{ ... }} expressions (244)

are identical.

A separate follow-up PR will address the actual bugs and dead code surfaced while reading the file (missing commas in a multi-selector rule, invalid CSS values like vertical-align: center and align-items: top, duplicated span.chargp/span.normgp/span.activesubgp rules, etc.) so this PR stays trivially reviewable.

Test plan

• git diff --word-diff shows only whitespace, brace, and newline changes
• Spot-check a few pages locally (homepage, a number field page, a modular form page, the knowls index) to confirm visual output is unchanged

🤖 Generated with Claude Code

[havarddj]

While we're cleaning up, it might make sense to fix inconsistencies in whitespace with jinja templates in this file:

{{foo}} vs
{{ foo}} vs
{{ foo }} 

see e.g. line 2474 in the new file.

[edgarcosta]

We should just write what style we want for Jinja and create a STYLE.md so we can try to follow it