migration list --linked fails to parse 8/10-digit migration versions as timestamps (Local/Remote mismatch display)

[CarMo11]

Summary
supabase migration list --linked --debug prints repeated parsing errors like:
parsing time "20251014" as "20060102150405": cannot parse "" as "15"
This occurs when migration versions are 8/10 digits (e.g. YYYYMMDD or YYYYMMDDNN) instead of 14-digit timestamps. Versions are strings, but the CLI tries to parse them into timestamps for display, which leads to confusing Local-only/Remote-only blanks in the output table (display issue).

Environment

• Supabase CLI: 2.72.7 (Homebrew)
• OS: macOS
• Remote Postgres: Supabase hosted (server_version=17.6 in debug)

Repro steps

1. Remote DB has supabase_migrations.schema_migrations.version entries like:
   • 20251014
   • 2025101401
   • 20260120
2. Local migrations directory contains matching files, e.g.:
   • supabase/migrations/20251014_events.sql
   • supabase/migrations/20260120_create_rpc_settle_match_bets.sql
3. Run:

supabase migration list --linked --debug | tail -n 120