fix(build): use fileURLToPath for cross-platform path comparison in esbuild

The esbuild config was comparing import.meta.url directly with process.argv[1]
to detect direct invocation. On Windows, this comparison always failed because:

- import.meta.url: `file:///D:/path/to/file.mjs` (forward slashes, triple slash)
- process.argv[1]: `D:\path\to\file.mjs` (backslashes)

This caused the build() function to never run on Windows. The script would
just export the config and exit with code 0, which is why the build reported
success without creating any files.

Fix: Use fileURLToPath(import.meta.url) to normalize the URL to a file path
that matches process.argv[1] on all platforms.

This was the root cause of all Windows CI failures - the build wasn't actually
running, so no dist/cli.js was created, causing ~180 tests to fail.

Author: jdalton

packages/cli/.config/esbuild.cli.build.mjs

@@ -371,7 +371,8 @@ const config = {
 }
 
 // Run build if invoked directly.
-if (import.meta.url === `file://${process.argv[1]}`) {
+// Use fileURLToPath to handle Windows paths correctly.
+if (fileURLToPath(import.meta.url) === process.argv[1]) {
   build(config).catch(error => {
     console.error('Build failed:', error)
     process.exitCode = 1