fix(test): add explicit logging for binary test suite execution

Add clear separator and status logging to show which binary is being
tested and whether it exists. This resolves confusion in CI logs when
multiple binaries are tested sequentially.

Output now shows:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Testing: [Binary Name]
Path: [path]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Binary exists: true/false
✓ Binary found and ready for testing (if exists)

This makes it immediately clear in CI logs:
- When SEA tests are being attempted after smol
- Whether each binary was found in cache
- Which tests are actually running vs skipping

Author: jdalton

packages/cli/test/integration/binary/binary-test-suite.test.mts

@@ -131,8 +131,16 @@ function runBinaryTestSuite(binaryType: keyof typeof BINARIES) {
     let binaryExists = false
 
     beforeAll(async () => {
+      // Log which binary we're testing.
+      logger.log('')
+      logger.log(`━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━`)
+      logger.log(`Testing: ${binary.name}`)
+      logger.log(`Path: ${binary.path}`)
+      logger.log(`━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━`)
+
       // Check if binary exists.
       binaryExists = existsSync(binary.path)
+      logger.log(`Binary exists: ${binaryExists}`)
 
       if (!binaryExists) {
         logger.log('')
@@ -192,6 +200,11 @@ function runBinaryTestSuite(binaryType: keyof typeof BINARIES) {
 
         logger.log(`Binary built successfully: ${binary.path}`)
         logger.log('')
+      } else {
+        // Binary already exists.
+        logger.log('')
+        logger.log(`✓ Binary found and ready for testing`)
+        logger.log('')
       }
 
       // Check authentication.