fix(cli): inject version into Go binary via ldflags

The legacy CLI shell forwards most commands to the bundled `supabase-go`
binary, whose upgrade banner reports the currently installed version
from `utils.Version` — a string assigned via `-ldflags -X` at compile
time. The Bun build script was missing that injection, so every release
shipped a Go binary with `utils.Version=""`, producing:

  A new version of Supabase CLI is available: v2.100.1 (currently installed v)

and triggering the upgrade prompt on every invocation (semver.Compare
treats the empty string as less than any valid version).

Restore the `-X github.com/supabase/cli/internal/utils.Version=...`
ldflag in `apps/cli/scripts/build.ts` so the npm version is baked into
the Go binary at build time, matching the prior `.goreleaser.yml`
behavior.

Fixes #5308

Author: Coly010

apps/cli/scripts/build.ts

@@ -125,7 +125,8 @@ async function buildGoTarget(target: (typeof TARGETS)[number]) {
   const outfile = path.join(binDir, `supabase-go${target.ext}`);
 
   console.log(`[${target.pkg}] Compiling Go CLI (${goos}/${goarch})...`);
-  await $`go build -trimpath -ldflags="-s -w" -o ${outfile} .`.cwd(goSource).env({
+  const goLdflags = `-s -w -X github.com/supabase/cli/internal/utils.Version=${version}`;
+  await $`go build -trimpath -ldflags=${goLdflags} -o ${outfile} .`.cwd(goSource).env({
     ...process.env,
     GOOS: goos,
     GOARCH: goarch,