Add standard library and modules

[uncenter]

Tracking issue. Splitting the original #1803 into multiple pull request steps.

• Add standard library feat(lib): add lib.less standard library #1843.
• Deploy standard library.
• Integrate standard library tree-wide refactor(tree-wide)!: integrate standard library #1846.
• Add and deploy MediaWiki library module.
  • Integrate MediaWiki library module for Wikipedia.
  • Integrate MediaWiki library module for wiki.nixos.org.

Potential Library Modules

Some originally mentioned in #1357.

• Google's M3 feat(lib): add m3.less standard library #1876 M3/M2 Google Web App discussion #1705
• Bootstrap (https://github.com/search?q=repo:catppuccin/userstyles%20--bs&type=code)
• Tailwind v3 (longer, must theme every class variant for each color - .bg-foo, .text-foo, etc.)
• Tailwind v4 (shorter, should be able to theme CSS variables only)
• Ace Editor (could be more useful as a separate port, currently used for pythonanywhere; https://github.com/search?q=org:catppuccin+.ace_editor&type=code)
• Prettylights (potentially useful as a separate port, https://github.com/wooorm/starry-night uses the same variables; https://github.com/search?q=org:catppuccin+color-prettylights&type=code)

[uncenter]

Adding on that we need to:

• Extend linting to library modules.
• Figure out dev server setup for testing library modules.

[uncenter]

Also:

• Standardize on "doc comments" format or docs pages on the website for library modules to explain API usage.
• Something in the documentation about what the standard library is, what the library modules are, how to change them, how/when to use them, etc.