Handle DROP VIEW cleanup and robust SQL parser spans

[nicosuave]

Summary

• add DROP VIEW lifecycle handling to measure-view catalog through FFI and extension hook
• harden SQL parsing in measures engine for quoted and qualified identifiers, alias parsing, and comment-aware whitespace handling
• replace parser span estimates with source-aware scanners for AGGREGATE calls and SELECT item ranges, including comment handling
• add regression tests for malformed DROP VIEW tails and comment-heavy span and alias cases

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 18f928eaed

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve schema when dropping measure views

This parser drops schema qualification by returning only the last identifier from DROP VIEW names, so DROP VIEW analytics.orders_v is treated the same as DROP VIEW orders_v. Because the catalog delete is keyed only by that unqualified name, a drop against a different schema can remove the wrong measure metadata and break subsequent AGGREGATE(...) queries for the still-existing view. Keep the full qualified name (or reject qualified drops) when mapping DROP statements to measure-view cleanup.

Useful? React with 👍 / 👎.