scope ParseSchema by object type to avoid duplicate trigger execution

[g0ldyy]

Summary

• scope ParseSchema after CREATE VIEW to type = 'view'
• scope materialized-view schema reload by object type as well
• prevent same-named triggers from being reparsed and duplicated during view creation
• add sqltest, integration, and simulator regressions

Reproduction

CREATE TABLE t(x INTEGER);
CREATE TABLE log(v INTEGER);
CREATE TRIGGER dup AFTER INSERT ON t BEGIN
    INSERT INTO log VALUES (NEW.x);
END;
CREATE VIEW dup AS SELECT x FROM t;
INSERT INTO t VALUES (1);
SELECT count(*), group_concat(v, ',') FROM log;

Expected SQLite result:

1|1

Before this patch, Turso returned:

2|1,1

Simulator

This PR extends the deterministic simulator with a targeted memory regression:

• runner::memory::view_trigger_parse_schema::sim_create_view_does_not_duplicate_same_named_trigger

It verifies the sequence under simulated async I/O and after reopen to ensure the duplicated trigger execution does not persist.

Tests

• cargo test -q -p core_tester --test integration_tests trigger::test_create_view_does_not_duplicate_same_named_trigger -- --exact --nocapture
• cargo run -q -p test-runner -- run testing/sqltests/tests/views.sqltest
• cargo test -q -p limbo_sim runner::memory::view_trigger_parse_schema::sim_create_view_does_not_duplicate_same_named_trigger -- --exact --nocapture

[turso-bot]

Please review @pereman2

[github-actions]

Fossier: Approved by Maintainer

Approved by @pthorpe92.

[PThorpe92]

/fossier approve