fix(indexes): accept --catalog on 'indexes delete'

[shefeek-jinnah]

Summary

hotdata indexes create scopes the table with --catalog <alias> (resolved to the backing connection — including a managed database's default_connection_id), but hotdata indexes delete accepted only a raw --connection-id. On a managed database, the only value that works is the default_connection_id from the original databases create response, which isn't surfaced by indexes list or any databases subcommand — so every natural input (catalog alias, database id, internal __db_* connection name) fails, making it effectively impossible to delete an index without having saved that response.

Fixes hotdata-dev/runtimedb#853 (cross-repo, won't auto-close).

Change

Give indexes delete the same --catalog flag and resolve_connection_id resolution that indexes create already uses:

• indexes delete --catalog <alias> --schema <s> --table <t> --name <idx> — resolves the catalog (or connection name) to the connection, mirroring create.
• --connection-id <id> is retained (mutually exclusive with --catalog) for the raw-id case.

No server change — the delete endpoint is unchanged; this is purely client-side connection resolution, closing the --catalog/--connection-id asymmetry between create and delete.

Verification

Built target/debug/hotdata and ran against a live workspace:

indexes create --catalog <cat> --schema public --table hits --name idx_id --column id --type sorted
  → Index created.

# before (this CLI, stock):
indexes delete --connection-id <cat> --schema public --table hits --name idx_id
  → Index 'idx_id' not found        # --connection-id can't take a catalog; no --catalog flag existed

# after (this PR):
indexes delete --catalog <cat> --schema public --table hits --name idx_id
  → Index 'idx_id' deleted.         # resolved catalog → connection, index gone from `indexes list`

cargo fmt --check clean; all existing tests pass; the edits add no new clippy warnings.

[claude]

super nit: indexes create defaults --schema to public (line 312), but delete leaves it as a no-default Option and errors when it's absent. So create --catalog x --table t --name idx works, yet the mirror delete --catalog x --table t --name idx fails asking for --schema. Since this PR's goal is to close the create/delete asymmetry, consider giving delete's schema the same default_value = "public". (not blocking)

Suggested change

	schema: Option<String>,
	/// Schema name (default: public)
	#[arg(long, default_value = "public")]
	schema: String,

[claude]

Closes the --catalog/--connection-id asymmetry cleanly; resolution mirrors indexes create. One non-blocking super nit on the --schema default left inline.

[codecov]

Codecov Report

❌ Patch coverage is 79.48718% with 16 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/main.rs	0.00%	15 Missing ⚠️
src/commands/indexes.rs	98.41%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[claude]

Mirrors indexes create's --catalog resolution cleanly; clap enforces the scope/exclusivity constraints and the new arg-parsing tests are meaningful. The prior super nit (defaulting delete's --schema to public) is implemented. LGTM.

[claude]

LGTM. indexes delete now mirrors create's --catalog resolution and defaults --schema to public, closing the asymmetry. Arg-parsing paths are well covered by the new tests.