Upgrade lightningcss to 1.29.2 in Standalone (#17169)

Closes #17162
Closes #17163
Closes #17164
Closes #17165
Closes #17166
Closes #17167

Noticed that there was a second place pulling in the lightningcss
version numbers that wasn't covered by the previous upgrade PR.
Thankfully the APIs of the node bindings are still compatible.

To avoid this mistake in the future I also exported these sub-packages
as a workspace dependency so all the version strings appear right next
to each other.

Author: philipp-spiess

packages/@tailwindcss-standalone/package.json

@@ -44,12 +44,12 @@
     "@parcel/watcher-win32-x64": "^2.5.1",
     "@types/bun": "^1.2.4",
     "bun": "^1.2.4",
-    "lightningcss-darwin-arm64": "^1.29.1",
-    "lightningcss-darwin-x64": "^1.29.1",
-    "lightningcss-linux-arm64-gnu": "^1.29.1",
-    "lightningcss-linux-arm64-musl": "^1.29.1",
-    "lightningcss-linux-x64-gnu": "^1.29.1",
-    "lightningcss-linux-x64-musl": "^1.29.1",
-    "lightningcss-win32-x64-msvc": "^1.29.1"
+    "lightningcss-darwin-arm64": "catalog:",
+    "lightningcss-darwin-x64": "catalog:",
+    "lightningcss-linux-arm64-gnu": "catalog:",
+    "lightningcss-linux-arm64-musl": "catalog:",
+    "lightningcss-linux-x64-gnu": "catalog:",
+    "lightningcss-linux-x64-musl": "catalog:",
+    "lightningcss-win32-x64-msvc": "catalog:"
   }
 }

pnpm-lock.yaml

@@ -7,6 +7,13 @@ packages:
 
 catalog:
   '@types/node': ^20.14.8
-  lightningcss: 1.29.2
   prettier: 3.5.0
   vite: ^6.0.0
+  lightningcss: 1.29.2
+  lightningcss-darwin-arm64: 1.29.2
+  lightningcss-darwin-x64: 1.29.2
+  lightningcss-linux-arm64-gnu: 1.29.2
+  lightningcss-linux-arm64-musl: 1.29.2
+  lightningcss-linux-x64-gnu: 1.29.2
+  lightningcss-linux-x64-musl: 1.29.2
+  lightningcss-win32-x64-msvc: 1.29.2