[Feature] Defer file-store validation until runtime initialization #10849

Search before asking

• I searched in the issues and found nothing similar.

Motivation

Stricter validation after an upgrade can make existing table options invalid. #10830 decoupled catalog alter and drop operations from runtime table loading, but Flink and Spark still load tables before executing SQL metadata commands.

Consequently, SHOW CREATE TABLE, ALTER TABLE, and DROP TABLE can still fail on runtime-invalid options, preventing users from inspecting, repairing, or deleting affected tables.

Solution

• Load file-store table definitions without initializing the runtime store, using the existing table-loading API
• Defer runtime validation and store creation until the first scan, read, write, or commit operation.
• Keep CREATE and ALTER validation before committing the resulting schema.

Anything else?

Follow-up to #10829 and #10830.

Are you willing to submit a PR?

• I'm willing to submit a PR!