test(cli-e2e): pack @sanity/cli-core alongside cli and create-sanity (#1040)

Without this, npm install resolves the @sanity/cli-core dependency
of the packed @sanity/cli from the npm registry, so e2e tests run
against the published version of cli-core instead of the local
source. This causes spurious failures whenever @sanity/cli starts
using new exports from cli-core that aren't yet published.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: binoy14

packages/@sanity/cli-e2e/globalSetup.ts

@@ -25,18 +25,25 @@ export async function setup(project: TestProject): Promise<void> {
       )
     }
   } else {
+    console.log('Packing @sanity/cli-core...')
+    const cliCoreTarball = packPackage('@sanity/cli-core')
+
     console.log('Packing @sanity/cli...')
     const cliTarball = packCli()
 
     console.log('Packing create-sanity...')
     const createSanityTarball = packPackage('create-sanity')
-    tarballPaths = [cliTarball, createSanityTarball]
+    tarballPaths = [cliCoreTarball, cliTarball, createSanityTarball]
 
     const tmpDir = mkdtempSync(join(tmpdir(), 'cli-e2e-'))
     cleanupDir = tmpDir
 
     console.log(`Installing tarballs into ${tmpDir}...`)
-    const binaryPath = installFromTarball([cliTarball, createSanityTarball], tmpDir, 'sanity')
+    const binaryPath = installFromTarball(
+      [cliCoreTarball, cliTarball, createSanityTarball],
+      tmpDir,
+      'sanity',
+    )
 
     process.env.E2E_BINARY_PATH = binaryPath
     console.log(`E2E_BINARY_PATH set to ${binaryPath}`)